From: Rusty Russell <rusty@rustcorp.com.au>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] Add virtio IDs file
Date: Mon, 3 Aug 2009 16:59:52 +0930 [thread overview]
Message-ID: <200908031659.52527.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A728E74.1070805@oss.ntt.co.jp>
On Fri, 31 Jul 2009 03:55:56 pm Fernando Luis Vázquez Cao wrote:
> Virtio IDs are spread all over the tree which makes assigning new IDs
> bothersome. Putting them together should make the process less error-prone.
>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
Seems like a good idea to me! Applied.
(I added a #ifndef _LINUX_VIRTIO_IDS_H wrapper around it, too).
Thanks!
Rusty.
PS. Whitespace damage in this and your previous patch? Fixed.
prev parent reply other threads:[~2009-08-03 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 6:25 [PATCH] Add virtio IDs file Fernando Luis Vázquez Cao
2009-08-03 7:29 ` Rusty Russell [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=200908031659.52527.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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