All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Fabiano Rosas <farosas@suse.de>,
	Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] migration/vmstate: remove VMSTATE_BUFFER_POINTER_UNSAFE macro
Date: Wed, 8 Oct 2025 11:35:59 -0400	[thread overview]
Message-ID: <aOaE3_qs8N24b-UN@x1.local> (raw)
In-Reply-To: <78e722ee-cd01-43f4-abfe-efc019cce48f@tls.msk.ru>

On Wed, Oct 08, 2025 at 11:10:19AM +0300, Michael Tokarev wrote:
> On 9/29/25 18:57, Peter Xu wrote:
> > On Sat, Aug 02, 2025 at 05:21:09PM +0300, Michael Tokarev wrote:
> > > The only user of this macro was VirtIONet.vlans, which has been
> > > converted to regular VMSTATE_BUFFER.
> ..
> > I'm scanning over lost patches on the list.  I suspect this is lost when
> > you sent v2 replying to v1.
> 
> This hasn't been lost due to v2 vs v1, - the reason was that the first
> patch in the series was trivial, while the second (this one) is a bit
> more than trivial, - so the first patch went through qemu-trivial, and
> the second went nowhere :)
> 
> > Wanna repost with a full v2 to catch Michael's attention once more?  I also
> > always would suggest a cover letter..
> Yeah, re-sending it is ok.  Dunno what's the reason for the cover letter
> though, for a single patch.
> 
> Thank you for your attention - I'd lost it myself without you ;)

We might have lost each other somehow.. :)

I am looking at this series that contains patch 1+2 on v1:

https://lore.kernel.org/all/20250802142115.41638-1-mjt@tls.msk.ru/

v2 of patch 1 was sent in a reply here:

https://lore.kernel.org/all/20250803085443.318611-1-mjt@tls.msk.ru/

As of today's git master branch (commit 37ad0e48e9), I still didn't see
patch 1 (v1 or v2) lands..

Thanks,

-- 
Peter Xu



  reply	other threads:[~2025-10-08 15:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02 14:21 [PATCH 1/2] virtio-net: make VirtIONet.vlans an array instead of a pointer Michael Tokarev
2025-08-02 14:21 ` [PATCH 2/2] migration/vmstate: remove VMSTATE_BUFFER_POINTER_UNSAFE macro Michael Tokarev
2025-08-03  9:50   ` Akihiko Odaki
2025-08-06 16:46   ` Philippe Mathieu-Daudé
2025-08-06 18:32   ` Peter Xu
2025-09-29 15:57   ` Peter Xu
2025-10-08  8:10     ` Michael Tokarev
2025-10-08 15:35       ` Peter Xu [this message]
2025-08-02 14:45 ` [PATCH 1/2] virtio-net: make VirtIONet.vlans an array instead of a pointer Michael Tokarev
2025-08-03  7:38   ` Akihiko Odaki
2025-08-06 16:49     ` Philippe Mathieu-Daudé
2025-08-03  8:54 ` [PATCH v2 " Michael Tokarev
2025-08-03  9:50   ` Akihiko Odaki
2025-08-06 11:00     ` Lei Yang
2025-08-06 16:49   ` Philippe Mathieu-Daudé

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=aOaE3_qs8N24b-UN@x1.local \
    --to=peterx@redhat.com \
    --cc=farosas@suse.de \
    --cc=mjt@tls.msk.ru \
    --cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
    --cc=qemu-devel@nongnu.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.