From: Stefan Hajnoczi <stefanha@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kevin Wolf <kwolf@redhat.com>,
pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] win32-aio: use iov utility functions instead of open-coding them
Date: Fri, 18 Jan 2013 10:00:02 +0100 [thread overview]
Message-ID: <20130118090002.GA20153@stefanha-thinkpad.hitronhub.home> (raw)
In-Reply-To: <1358434072-9637-1-git-send-email-mjt@msgid.tls.msk.ru>
On Thu, Jan 17, 2013 at 06:47:52PM +0400, Michael Tokarev wrote:
> We have iov_from_buf() and iov_to_buf(), use them instead of
> open-coding these in block/win32-aio.c
> ---
> v3: added the forgotten #include (compile-tested on mingw32)
> v2: rebase on top of the fix from bonzini@
>
> block/win32-aio.c | 17 +++--------------
> 1 file changed, 3 insertions(+), 14 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2013-01-18 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 14:47 [Qemu-devel] [PATCH v3] win32-aio: use iov utility functions instead of open-coding them Michael Tokarev
2013-01-18 9:00 ` 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=20130118090002.GA20153@stefanha-thinkpad.hitronhub.home \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@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).