From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Subject: Re: [PULL] lguest & virtio
Date: Mon, 28 Sep 2009 12:20:25 +0930 [thread overview]
Message-ID: <200909281220.26266.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090926150124.GA11623@lst.de>
On Sun, 27 Sep 2009 12:31:24 am Christoph Hellwig wrote:
> What happend to the patch to drop the virt/non-rotational flag?
I pushed it back; I realize now you still wanted that one, it was
"Subject: virtio_blk: set QUEUE_ORDERED_DRAIN by default" you wanted to
reconsider.
Will send separately now...
Rusty.
next prev parent reply other threads:[~2009-09-28 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 13:05 [PULL] lguest & virtio Rusty Russell
2009-09-26 15:01 ` Christoph Hellwig
2009-09-28 2:50 ` Rusty Russell [this message]
2009-09-28 3:36 ` [PATCH] virtio_blk: revert QUEUE_FLAG_VIRT addition Rusty Russell
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=200909281220.26266.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=fernando@oss.ntt.co.jp \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiaoguangrong@cn.fujitsu.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 read-only IMAP folder(s) and NNTP newsgroup(s).