From: Christoph Hellwig <hch@lst.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] fix asynchronous ioctls
Date: Mon, 4 May 2009 17:06:25 +0200 [thread overview]
Message-ID: <20090504150625.GA9963@lst.de> (raw)
In-Reply-To: <20090501142003.GA11017@lst.de>
On Fri, May 01, 2009 at 04:20:04PM +0200, Christoph Hellwig wrote:
> 2/2 is the SG_IO passthrough which I accidentally sent as reply to the
> previous version.
Any reason you pulled in the SG_IO passthrough but not this patch?
It's not going to work without it :)
Also the commits list seems to be a lagging a little bit, can't find
messages for at least the two patches you applied from me.
prev parent reply other threads:[~2009-05-04 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:57 [Qemu-devel] [PATCH 1/2] fix asynchronous ioctls Christoph Hellwig
2009-05-01 13:55 ` Anthony Liguori
2009-05-01 14:20 ` Christoph Hellwig
2009-05-04 15:06 ` Christoph Hellwig [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=20090504150625.GA9963@lst.de \
--to=hch@lst.de \
--cc=anthony@codemonkey.ws \
--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).