qemu-devel.nongnu.org archive mirror
 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: Mon, 29 Sep 2025 11:57:16 -0400	[thread overview]
Message-ID: <aNqsXPt3LGJv4F1O@x1.local> (raw)
In-Reply-To: <20250802142115.41638-2-mjt@tls.msk.ru>

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.
> 
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> ---
>  include/migration/vmstate.h | 9 ---------
>  1 file changed, 9 deletions(-)
> 
> diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
> index 1ff7bd9ac4..ec0946c2aa 100644
> --- a/include/migration/vmstate.h
> +++ b/include/migration/vmstate.h
> @@ -702,15 +702,6 @@ extern const VMStateInfo vmstate_info_qlist;
>      .offset     = offsetof(_state, _field),                          \
>  }
>  
> -#define VMSTATE_BUFFER_POINTER_UNSAFE(_field, _state, _version, _size) { \
> -    .name       = (stringify(_field)),                               \
> -    .version_id = (_version),                                        \
> -    .size       = (_size),                                           \
> -    .info       = &vmstate_info_buffer,                              \
> -    .flags      = VMS_BUFFER|VMS_POINTER,                            \
> -    .offset     = offsetof(_state, _field),                          \
> -}
> -
>  /* Allocate a temporary of type 'tmp_type', set tmp->parent to _state
>   * and execute the vmsd on the temporary.  Note that we're working with
>   * the whole of _state here, not a field within it.
> -- 
> 2.47.2
> 

I'm scanning over lost patches on the list.  I suspect this is lost when
you sent v2 replying to v1.

Wanna repost with a full v2 to catch Michael's attention once more?  I also
always would suggest a cover letter..

Thanks,

-- 
Peter Xu



  parent reply	other threads:[~2025-09-29 15:58 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 [this message]
2025-10-08  8:10     ` Michael Tokarev
2025-10-08 15:35       ` Peter Xu
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=aNqsXPt3LGJv4F1O@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 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).