From: Peter Xu <peterx@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v2 2/2] migration/vmstate: remove VMSTATE_BUFFER_POINTER_UNSAFE macro
Date: Thu, 23 Oct 2025 10:33:12 -0400 [thread overview]
Message-ID: <aPo8qL4zg3LEXMpq@x1.local> (raw)
In-Reply-To: <20251023135316.31128-3-mjt@tls.msk.ru>
On Thu, Oct 23, 2025 at 04:53:10PM +0300, Michael Tokarev wrote:
> The only user of this macro was VirtIONet.vlans, which has been
> converted to regular VMSTATE_BUFFER.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2025-10-23 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 13:53 [PATCH v2 0/2] virtio-net: make VirtIONet.vlans an array instead of a pointer Michael Tokarev
2025-10-23 13:53 ` [PATCH v2 1/2] " Michael Tokarev
2025-10-23 13:53 ` [PATCH v2 2/2] migration/vmstate: remove VMSTATE_BUFFER_POINTER_UNSAFE macro Michael Tokarev
2025-10-23 14:33 ` Peter Xu [this message]
2025-10-23 14:46 ` Philippe Mathieu-Daudé
2025-10-27 19:13 ` [PATCH v2 0/2] virtio-net: make VirtIONet.vlans an array instead of a pointer 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=aPo8qL4zg3LEXMpq@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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 NNTP newsgroup(s).