qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-ehci: move device/vendor/class id to qdev
Date: Wed, 15 Jun 2011 09:48:49 +0300	[thread overview]
Message-ID: <20110615064849.GA31097@redhat.com> (raw)
In-Reply-To: <4DF85212.4010808@redhat.com>

On Wed, Jun 15, 2011 at 08:32:50AM +0200, Gerd Hoffmann wrote:
> On 06/14/11 19:40, Michael S. Tsirkin wrote:
> >This is on top of my pci tree.
> 
> Looks good.  Wanna queue this up in your PCI tree, so all devices
> are switched over at once when this is merged?
> 
> cheers,
>   Gerd

Guess so, yes.
Thanks for the review.

-- 
MST

      reply	other threads:[~2011-06-15  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 17:40 [Qemu-devel] [PATCH] usb-ehci: move device/vendor/class id to qdev Michael S. Tsirkin
2011-06-15  6:32 ` Gerd Hoffmann
2011-06-15  6:48   ` Michael S. Tsirkin [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=20110615064849.GA31097@redhat.com \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --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).