From: Kevin Wolf <kwolf@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 6/6] atapi: Save / load the new GESN event states during migration
Date: Tue, 12 Apr 2011 12:43:00 +0200 [thread overview]
Message-ID: <4DA42CB4.2080607@redhat.com> (raw)
In-Reply-To: <618d52d111bc5657efc46d78e76f15c80d077ac4.1302600061.git.amit.shah@redhat.com>
Am 12.04.2011 11:27, schrieb Amit Shah:
> Add a new subsection to save and restore the events state for the
> GET_EVENT_STATUS_NOTIFICATION command.
>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
Looks good, but I think it should be merged into patch 5, so that there
are no commits for which migration is broken.
Kevin
prev parent reply other threads:[~2011-04-12 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 9:27 [Qemu-devel] [PATCH v2 0/6] atapi: Implement 'media' subcommand for GESN Amit Shah
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 1/6] atapi: Allow GESN after media change Amit Shah
2011-04-12 9:54 ` Kevin Wolf
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 2/6] atapi: Move GET_EVENT_STATUS_NOTIFICATION command handling to its own function Amit Shah
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 3/6] atapi: GESN: Spin off No Event Available handling into " Amit Shah
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 4/6] atapi: GESN: Use structs for commonly-used field types Amit Shah
2011-04-12 10:07 ` Kevin Wolf
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 5/6] atapi: GESN: implement 'media' subcommand Amit Shah
2011-04-12 10:41 ` Kevin Wolf
2011-04-12 9:27 ` [Qemu-devel] [PATCH v2 6/6] atapi: Save / load the new GESN event states during migration Amit Shah
2011-04-12 10:43 ` Kevin Wolf [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=4DA42CB4.2080607@redhat.com \
--to=kwolf@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).