From: Stefan Hajnoczi <stefanha@gmail.com>
To: Amos Kong <akong@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vmstate: fix varrays with uint32_t indexes
Date: Tue, 12 Apr 2011 10:57:22 +0100 [thread overview]
Message-ID: <BANLkTi=2cLoGa3QJCKp0cJUdvfJtM7Y98A@mail.gmail.com> (raw)
In-Reply-To: <20110411140143.7200.71424.stgit@localhost6.localdomain6>
On Mon, Apr 11, 2011 at 3:01 PM, Amos Kong <akong@redhat.com> wrote:
> VARRAY_UINT32 only exists in vmstate_load_state(),
> but not in vmstate_save_state().
>
> CC: Juan Quintela <quintela@redhat.com>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> savevm.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
Hmm...Juan wasn't actually CCed on the email. Fixed.
Stefan
prev parent reply other threads:[~2011-04-12 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 14:01 [Qemu-devel] [PATCH] vmstate: fix varrays with uint32_t indexes Amos Kong
2011-04-12 9:57 ` Stefan Hajnoczi [this message]
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='BANLkTi=2cLoGa3QJCKp0cJUdvfJtM7Y98A@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).