From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
aik@ozlabs.ru, jan.kiszka@siemens.com, qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL] pci,msi,virtio
Date: Tue, 24 Jul 2012 13:32:06 +0200 [thread overview]
Message-ID: <500E87B6.2060507@suse.de> (raw)
In-Reply-To: <1343068192.2229.284.camel@bling.home>
Am 23.07.2012 20:29, schrieb Alex Williamson:
> On Mon, 2012-07-23 at 13:16 -0500, Anthony Liguori wrote:
>> On 07/23/2012 12:05 PM, Alex Williamson wrote:
>>> Looks like it merged ok for me, but you'll need this to complete the
>>> PCIUnregisterFunc conversion. Not sure how this built in MST's tree.
>>> Anthony, it'd be great if we could merge and fix this in your tree since
>>> MST is out of the office.
>>
>> I can't fix it without rewriting git history or breaking bisection which isn't
>> something I'm really willing to do.
>>
>> When does MST get back? If it's not for a while, I can merge it all manually
>> with a fixup.
>
> Next week, so (unfortunately for me) probably not worth you messing with
> it.
So Anthony, how urgent is your/Wanpeng's i440fx rework and through whose
queue is that supposed to go? Can you wait for mst's return? Or do you
want to handle it yourself and have mst rebase on it while at it?
My pci-host branch [1] is updated with mst's requested spapr_pci.c code
movement, so I just need to know whether to rebase on some other branch
and when to re-post. Soft Freeze is in three weeks iirc.
Regards,
Andreas
[1] http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/pci-host
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-07-24 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 15:15 [Qemu-devel] [PULL] pci,msi,virtio Michael S. Tsirkin
2012-07-23 16:09 ` Andreas Färber
2012-07-23 16:39 ` Anthony Liguori
2012-07-23 16:47 ` Andreas Färber
2012-07-23 17:05 ` Alex Williamson
2012-07-23 18:16 ` Anthony Liguori
2012-07-23 18:29 ` Alex Williamson
2012-07-24 11:32 ` Andreas Färber [this message]
2012-07-25 1:56 ` Alexey Kardashevskiy
2012-07-25 9:16 ` Andreas Färber
2012-07-29 13:58 ` Michael S. Tsirkin
2012-07-29 14:17 ` Michael S. Tsirkin
2012-07-29 14:21 ` 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=500E87B6.2060507@suse.de \
--to=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mst@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).