From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Jon Maloy <jmaloy@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH] migrate: Rename v1 address functions to v2 for clarity
Date: Thu, 5 Mar 2026 12:27:52 +1100 [thread overview]
Message-ID: <aajcGJ49H8VT9i0P@zatzit> (raw)
In-Reply-To: <20260305013858.7e079019@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On Thu, Mar 05, 2026 at 01:38:59AM +0100, Stefano Brivio wrote:
> On Tue, 3 Mar 2026 14:04:46 -0500
> Jon Maloy <jmaloy@redhat.com> wrote:
>
> > Some migration address structures and functions have a _v1 suffix.
> > This is confusing, since they are currently handling version 2 of
> > the migration protocol. We are soon going to introduce a new version
> > 3 of the protocol, so we choose to give these functions the correct
> > suffix _v2 instead. This is in correspondence with current reality,
> > and will help make a clearer distinction between the old and the new
> > versions of those functions.
> >
> > Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
>
> Applied.
>
> By the way, I think that adding david@gibson.dropbear.id.au in To: for
> these patches and series is enough to reach David.
It is, yes. I prefer to use my upstream address for upstream patches,
so I ignore the copies to the RH email.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-03-05 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 19:04 Jon Maloy
2026-03-05 0:38 ` Stefano Brivio
2026-03-05 1:27 ` David Gibson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aajcGJ49H8VT9i0P@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).