From: minyard@acm.org
To: "Dr . David Alan Gilbert" <dgilbert@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 0/3] ipmi: Fix vmstate transfer
Date: Wed, 25 Apr 2018 10:27:29 -0500 [thread overview]
Message-ID: <1524670052-28373-1-git-send-email-minyard@acm.org> (raw)
I was going to just re-send the previous versions of these, but after
looking I realized it would have the same misuse of vmstate_register(),
and I didn't have a way to work around it. I had already done the
VMSTATE_VSTRUCT work earlier, so I merged that in.
Changes from v2:
* Added VMSTATE_VSTRUCT types of vmstate macros that allow the
specific structure version used to be specified.
* Reworked the KCS vmstate code to use the new VMSTATE_VSTRUCT
macros.
Changes from v1:
* Validate the data values in pre_load functions.
* For KCS, instead of an old function, create a separate vmstate
structure for the new version. The name on the old vmstate
structure wasn't specific enough, so a new name was needed,
The old structure is set up to never be sent, but it can be
received.
next reply other threads:[~2018-04-25 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:27 minyard [this message]
2018-04-25 15:27 ` [Qemu-devel] [PATCH v3 1/3] vmstate: Add a VSTRUCT type minyard
2018-04-25 15:27 ` [Qemu-devel] [PATCH v3 2/3] ipmi: Use proper struct reference for KCS vmstate minyard
2018-05-18 15:45 ` Marc-André Lureau
2018-05-23 17:46 ` Corey Minyard
2018-04-25 15:27 ` [Qemu-devel] [PATCH v3 3/3] ipmi: Use proper struct reference for BT vmstate minyard
2018-04-25 20:27 ` Philippe Mathieu-Daudé
2018-04-25 21:15 ` Corey Minyard
2018-04-25 15:33 ` [Qemu-devel] [PATCH v3 0/3] ipmi: Fix vmstate transfer no-reply
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=1524670052-28373-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=dgilbert@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 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).