From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [patch 0/2] Fix and enhance virtio device id matching
Date: Wed, 27 May 2009 12:11:17 +0930 [thread overview]
Message-ID: <200905271211.17581.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090526134608.545964000@de.ibm.com>
On Tue, 26 May 2009 11:16:08 pm Christian Borntraeger wrote:
> Hello Rusty,
>
> here are two patches that change the device matching of the virtio bus.
> The patches have been refreshed agains linux-next and should apply
> to your private virtio tree.
>
> OK for linux-next?
Sure, added.
Thanks!
Rusty.
prev parent reply other threads:[~2009-05-27 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 13:46 [patch 0/2] Fix and enhance virtio device id matching Christian Borntraeger
2009-05-26 13:46 ` [patch 1/2] virtio: fix id_matching for virtio drivers Christian Borntraeger
2009-05-26 13:46 ` [patch 2/2] virtio: enhance " Christian Borntraeger
2009-05-27 2:41 ` 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=200905271211.17581.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=borntraeger@de.ibm.com \
--cc=kvm@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