qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH v3 0/3] block: warn about aio=native if libaio is unavailable
Date: Thu, 23 Jul 2015 13:48:33 +0100	[thread overview]
Message-ID: <1437655716-11623-1-git-send-email-stefanha@redhat.com> (raw)

v3:
 * Fix Patch 2 commit description because the mention of raw-posix.c ignored
   Windows [Markus]
 * Drop #ifdef CONFIG_LINUX_AIO from qemu-nbd.c

v2:
 * Banish CONFIG_LINUX_AIO from blockdev.c, that is raw-posix.c's business
   [Kevin]
 * Print the warning in the same way as the aio=native,cache.direct=off
   deprecation warning [Kevin]

Stefan Hajnoczi (3):
  raw-posix: warn about BDRV_O_NATIVE_AIO if libaio is unavailable
  blockdev: always compile in -drive aio= parsing
  qemu-nbd: always compile in --aio=MODE option

 block/raw-posix.c | 11 ++++++++++-
 blockdev.c        |  2 --
 qemu-nbd.c        |  8 --------
 3 files changed, 10 insertions(+), 11 deletions(-)

-- 
2.4.3

             reply	other threads:[~2015-07-23 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 12:48 Stefan Hajnoczi [this message]
2015-07-23 12:48 ` [Qemu-devel] [PATCH v3 1/3] raw-posix: warn about BDRV_O_NATIVE_AIO if libaio is unavailable Stefan Hajnoczi
2015-07-23 12:48 ` [Qemu-devel] [PATCH v3 2/3] blockdev: always compile in -drive aio= parsing Stefan Hajnoczi
2015-07-23 12:48 ` [Qemu-devel] [PATCH v3 3/3] qemu-nbd: always compile in --aio=MODE option Stefan Hajnoczi
2015-07-23 14:45 ` [Qemu-devel] [PATCH v3 0/3] block: warn about aio=native if libaio is unavailable Markus Armbruster
2015-07-24 13:21 ` Kevin Wolf

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=1437655716-11623-1-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).