From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: acpi_piix4: expose no_hotplug attribute via i/o port
Date: Thu, 6 Jan 2011 16:48:51 -0200 [thread overview]
Message-ID: <20110106184851.GA12327@amt.cnet> (raw)
In-Reply-To: <20110105193239.GA27817@redhat.com>
On Wed, Jan 05, 2011 at 09:32:39PM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 08, 2010 at 03:11:36PM -0200, Marcelo Tosatti wrote:
> >
> > On top of "add hotplug opt-out option for devices" patchset
> > http://www.mail-archive.com/qemu-devel@nongnu.org/msg46953.html.
> >
> > Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> >
> > diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
>
> Um, this does not seem to apply to master.
> It's at 23979dc5411befabe9049e37075b2b6320debc4e for me.
> What am I doing wrong?
It applies on top of the PCI no_hotplug patches from Gerd. Once you have
those in the pci branch, i can regenerate this one and retest.
These should not go through the uq/master branch, that is a KVM support
code specific branch.
Thanks.
prev parent reply other threads:[~2011-01-06 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 17:11 [Qemu-devel] acpi_piix4: expose no_hotplug attribute via i/o port Marcelo Tosatti
2010-12-20 17:09 ` [Qemu-devel] document QEMU<->ACPIBIOS PCI hotplug interface Marcelo Tosatti
2010-12-20 20:11 ` Blue Swirl
2010-12-21 14:39 ` Marcelo Tosatti
2010-12-21 14:41 ` [Qemu-devel] PATCH: document QEMU<->ACPIBIOS PCI hotplug interface (v2) Marcelo Tosatti
2010-12-21 14:50 ` [Qemu-devel] " Avi Kivity
2011-01-05 16:00 ` [Qemu-devel] Re: acpi_piix4: expose no_hotplug attribute via i/o port Michael S. Tsirkin
2011-01-05 16:02 ` Michael S. Tsirkin
2011-01-05 19:32 ` Michael S. Tsirkin
2011-01-06 18:48 ` Marcelo Tosatti [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=20110106184851.GA12327@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@redhat.com \
--cc=kraxel@redhat.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).