From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Carsten Otte <cotte@de.ibm.com>,
markmc@redhat.com, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Isaku Yamahata <yamahata@valinux.co.jp>,
kraxel@redhat.com, Avi Kivity <avi@redhat.com>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: what's on qemu tree for pci related fixes
Date: Thu, 26 Nov 2009 18:15:02 +0200 [thread overview]
Message-ID: <20091126161502.GA2816@redhat.com> (raw)
In-Reply-To: <4B095B84.3020104@codemonkey.ws>
On Sun, Nov 22, 2009 at 09:40:52AM -0600, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>> Here's the list of patches on my pci fixes tree:
>> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git pci
>>
>> Here are the pci fixes I know of that haven't been applied already.
>> They mostly fix up minor nits. All, any more comments on any of them?
>> If yes, please reply on the original patch, not here.
>>
>
> Most of these are in staging minus Isaku's latest series. The last
> series caused some gnarly regressions so I've got them in a separate
> branch for more thorough testing.
>
> Regards,
>
> Anthony Liguori
Hope these are on their way to staging now as well.
I prefer building on top of these cleanups.
--
MST
next prev parent reply other threads:[~2009-11-26 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 15:19 [Qemu-devel] what's on qemu tree for pci related fixes Michael S. Tsirkin
2009-11-22 15:40 ` [Qemu-devel] " Anthony Liguori
2009-11-22 16:04 ` Michael S. Tsirkin
2009-11-26 16:15 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-05 14:51 [Qemu-devel] " Michael S. Tsirkin
2009-10-05 15:45 ` [Qemu-devel] " Anthony Liguori
2009-10-05 20:24 ` Michael S. Tsirkin
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=20091126161502.GA2816@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=markmc@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).