From: Mark McLoughlin <markmc@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] replace duplicated code.
Date: Thu, 18 Jun 2009 08:39:53 +0100 [thread overview]
Message-ID: <1245310793.675.47.camel@blaa> (raw)
In-Reply-To: <1245279129-6768-1-git-send-email-glommer@redhat.com>
On Wed, 2009-06-17 at 18:52 -0400, Glauber Costa wrote:
> pci_register_simple() does exactly the same of great part of the code
> in pci nic initialization. Replace it.
>
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> ---
> hw/pci.c | 12 ++++--------
> hw/qdev.c | 1 +
> 2 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index baffadd..0169b78 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -818,20 +818,16 @@ static const char * const pci_nic_names[] = {
> PCIDevice *pci_nic_init(PCIBus *bus, NICInfo *nd, int devfn,
> const char *default_model)
> {
> - DeviceState *dev;
> int i;
>
> qemu_check_nic_model_list(nd, pci_nic_models, default_model);
>
> for (i = 0; pci_nic_models[i]; i++) {
> if (strcmp(nd->model, pci_nic_models[i]) == 0) {
> - dev = qdev_create(&bus->qbus, pci_nic_names[i]);
> - qdev_set_prop_int(dev, "devfn", devfn);
> - qdev_set_prop_ptr(dev, "name", (void *)pci_nic_names[i]);
So, this patch depends on your "allow for name property" patch - resend
as a series, maybe with this one first?
> - qdev_set_netdev(dev, nd);
> - qdev_init(dev);
> - nd->private = dev;
> - return (PCIDevice *)dev;
> + PCIDevice *d;
> + d = pci_create_simple(bus, devfn, pci_nic_names[i]);
> + qdev_set_netdev((DeviceState *)d, nd);
I'd prefer &d->qdev here for type safety.
Cheers,
Mark.
next prev parent reply other threads:[~2009-06-18 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 22:52 [Qemu-devel] [PATCH] replace duplicated code Glauber Costa
2009-06-18 7:39 ` Mark McLoughlin [this message]
2009-06-18 9:48 ` Gerd Hoffmann
2009-06-18 13:59 ` Glauber Costa
2009-06-18 14:33 ` Gerd Hoffmann
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=1245310793.675.47.camel@blaa \
--to=markmc@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@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).