From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] blockdev: Rename BlockdevAction -> TransactionAction
Date: Mon, 13 May 2013 14:35:22 +0200 [thread overview]
Message-ID: <20130513123522.GA22258@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1368434774-13950-1-git-send-email-kwolf@redhat.com>
On Mon, May 13, 2013 at 10:46:14AM +0200, Kevin Wolf wrote:
> There's no reason to restrict transactions to operations related to
> block devices, so rename the type now before schema introspection stops
> us from doing so.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> blockdev.c | 22 +++++++++++-----------
> qapi-schema.json | 8 ++++----
> 2 files changed, 15 insertions(+), 15 deletions(-)
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
next prev parent reply other threads:[~2013-05-13 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 8:46 [Qemu-devel] [PATCH] blockdev: Rename BlockdevAction -> TransactionAction Kevin Wolf
2013-05-13 12:35 ` Stefan Hajnoczi [this message]
2013-05-13 12:51 ` Eric Blake
2013-05-13 14:53 ` Stefan Hajnoczi
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=20130513123522.GA22258@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@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).