From: "Andreas Färber" <afaerber@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
jan.kiszka@siemens.com, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>,
Alex Williamson <alex.williamson@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL] pci,msi,virtio
Date: Wed, 25 Jul 2012 11:16:24 +0200 [thread overview]
Message-ID: <500FB968.6020001@suse.de> (raw)
In-Reply-To: <500F5246.6090405@ozlabs.ru>
Am 25.07.2012 03:56, schrieb Alexey Kardashevskiy:
> On 24/07/12 21:32, Andreas Färber wrote:
>> 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.
>
>
> A bit curious - where is spapr_pci.c going to be moved to?
Code movement, not file movement. You can see the patches in the link
below. The above referred to code moved from patch 1 to the spapr_pci
patch - Ben was previously cc'ed on the cover letter but despite my
complaining no one added the sPAPR machine to MAINTAINERS, so the
individual patches don't show up on qemu-ppc.
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-25 9:16 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
2012-07-25 1:56 ` Alexey Kardashevskiy
2012-07-25 9:16 ` Andreas Färber [this message]
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=500FB968.6020001@suse.de \
--to=afaerber@suse.de \
--cc=agraf@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).