All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Alexandr Moshkov <dtalexundeer@yandex-team.ru>
Subject: [PATCH 1/4] migration: Remove VMSTATE_ARRAY_INT32_UNSAFE
Date: Wed, 29 Jul 2026 19:52:24 -0300	[thread overview]
Message-ID: <20260729225227.1170574-2-farosas@suse.de> (raw)
In-Reply-To: <20260729225227.1170574-1-farosas@suse.de>

The ARRAY_INT32_UNSAFE vmstate macro is not used anywhere. Remove it.

Signed-off-by: Fabiano Rosas <farosas@suse.de>
---
 include/migration/vmstate.h | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
index 1b7f295417e..92a1a9fe98e 100644
--- a/include/migration/vmstate.h
+++ b/include/migration/vmstate.h
@@ -451,15 +451,6 @@ extern const VMStateInfo vmstate_info_g_byte_array;
     .offset     = vmstate_offset_sub_array(_state, _field, _type, _start), \
 }
 
-#define VMSTATE_ARRAY_INT32_UNSAFE(_field, _state, _field_num, _info, _type) {\
-    .name       = (stringify(_field)),                               \
-    .num_offset = vmstate_offset_value(_state, _field_num, int32_t), \
-    .info       = &(_info),                                          \
-    .size       = sizeof(_type),                                     \
-    .flags      = VMS_VARRAY_INT32,                                  \
-    .offset     = vmstate_offset_varray(_state, _field, _type),      \
-}
-
 #define VMSTATE_VARRAY_INT32(_field, _state, _field_num, _version, _info, _type) {\
     .name       = (stringify(_field)),                               \
     .version_id = (_version),                                        \
-- 
2.53.0



  reply	other threads:[~2026-07-29 22:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 22:52 [PATCH 0/4] migration: Remove extra type-checking from vmstate macros Fabiano Rosas
2026-07-29 22:52 ` Fabiano Rosas [this message]
2026-07-30  8:07   ` [PATCH 1/4] migration: Remove VMSTATE_ARRAY_INT32_UNSAFE Vladimir Sementsov-Ogievskiy
2026-07-29 22:52 ` [PATCH 2/4] migration: Introduce VMStateOffset Fabiano Rosas
2026-07-30  8:06   ` Vladimir Sementsov-Ogievskiy
2026-07-30 14:45     ` Fabiano Rosas
2026-07-31 14:02     ` Fabiano Rosas
2026-07-31 15:59       ` Peter Xu
2026-07-31 16:19         ` Fabiano Rosas
2026-07-31 16:33           ` Fabiano Rosas
2026-07-30 14:35   ` Michael S. Tsirkin
2026-07-30 15:15     ` Fabiano Rosas
2026-07-30 15:23     ` Peter Xu
2026-07-29 22:52 ` [PATCH 3/4] migration: Remove redundant flags Fabiano Rosas
2026-07-30  8:11   ` Vladimir Sementsov-Ogievskiy
2026-07-30  8:23     ` Vladimir Sementsov-Ogievskiy
2026-07-29 22:52 ` [PATCH 4/4] migration: Remove duplicate vmstate macros Fabiano Rosas
2026-07-30  8:19   ` Vladimir Sementsov-Ogievskiy
2026-07-30  8:22 ` [PATCH 0/4] migration: Remove extra type-checking from " Vladimir Sementsov-Ogievskiy
2026-07-30 14:09 ` Peter Xu
2026-07-30 14:22   ` Peter Xu
2026-07-30 14:45     ` Michael S. Tsirkin
2026-07-30 15:50     ` Fabiano Rosas
2026-07-30 16:31       ` Peter Xu
2026-07-30 15:37   ` Fabiano Rosas
2026-07-30 16:16     ` Peter Xu

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=20260729225227.1170574-2-farosas@suse.de \
    --to=farosas@suse.de \
    --cc=dtalexundeer@yandex-team.ru \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --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.