From: Christoph Hellwig <hch@lst.de>
To: john cooper <john.cooper@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] Add serial number support for virtio_blk, V4
Date: Sun, 31 May 2009 13:07:17 +0200 [thread overview]
Message-ID: <20090531110716.GA13833@lst.de> (raw)
In-Reply-To: <4A1F615F.1090701@redhat.com>
On Fri, May 29, 2009 at 12:15:27AM -0400, john cooper wrote:
> virtio_blk-serial-4.patch
>
>
The patch looks good to me, but to get it applied to the kernel tree the
patch needs a good description and we also need your Signed-off-by line (See
Documentation/SubmittingPatches in the kernel source tree)
next prev parent reply other threads:[~2009-05-31 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 4:15 [Qemu-devel] [PATCH 2/2] Add serial number support for virtio_blk, V4 john cooper
2009-05-31 11:07 ` Christoph Hellwig [this message]
2009-06-01 7:10 ` [Qemu-devel] " Rusty Russell
2009-06-03 10:17 ` Jens Axboe
2009-06-03 15:08 ` john cooper
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=20090531110716.GA13833@lst.de \
--to=hch@lst.de \
--cc=john.cooper@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).