From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Revert "PCI: Convert pci_device_hot_add() to QObject"
Date: Mon, 26 Apr 2010 15:21:37 -0300 [thread overview]
Message-ID: <20100426152137.34ee9fbe@redhat.com> (raw)
In-Reply-To: <m3vdbexg5o.fsf@blackfin.pond.sub.org>
On Mon, 26 Apr 2010 19:44:19 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> We don't want pci_add in QMP. Use device_add instead.
>
> This reverts commit 7a344f7ac7bb651d0556a933ed8060d3a9e5d949.
>
> Conflicts:
>
> hw/pci-hotplug.c
> sysemu.h
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
The patch looks ok and I'm assuming that device_add can do everything
pci_add does, right?
next prev parent reply other threads:[~2010-04-26 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 17:44 [Qemu-devel] [PATCH] Revert "PCI: Convert pci_device_hot_add() to QObject" Markus Armbruster
2010-04-26 18:21 ` Luiz Capitulino [this message]
2010-05-03 9:29 ` [Qemu-devel] " Markus Armbruster
2010-05-03 16:59 ` Anthony Liguori
2010-05-04 8:38 ` Markus Armbruster
2010-05-04 9:26 ` Daniel P. Berrange
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=20100426152137.34ee9fbe@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@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).