From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
peter.maydell@linaro.org,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] nand: Don't use qdev_create() in nand_init()
Date: Wed, 5 Feb 2014 15:56:23 +0100 [thread overview]
Message-ID: <20140205155623.772a6c35@thinkpad> (raw)
In-Reply-To: <1391610653-13439-1-git-send-email-afaerber@suse.de>
On Wed, 5 Feb 2014 15:30:53 +0100
Andreas Färber <afaerber@suse.de> wrote:
> Commit 7426aa72c36c908a7d0eae3e38568bb0a70de479 (nand: Don't inherit
> from Sysbus) changed the parent type of TYPE_NAND but continued to use
> qdev_create(), which handled a NULL BusState as SysBus.
>
> Use object_new() instead, and reuse the TYPE_NAND define while at it.
>
> Reported-by: Markus Armbruster <armbru@redhat.com>
> Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> hw/block/nand.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/block/nand.c b/hw/block/nand.c
> index a871ce0..6d7c804 100644
> --- a/hw/block/nand.c
> +++ b/hw/block/nand.c
> @@ -632,7 +632,7 @@ DeviceState *nand_init(BlockDriverState *bdrv, int manf_id, int chip_id)
> if (nand_flash_ids[chip_id].size == 0) {
> hw_error("%s: Unsupported NAND chip ID.\n", __FUNCTION__);
> }
> - dev = qdev_create(NULL, "nand");
> + dev = DEVICE(object_new(TYPE_NAND));
> qdev_prop_set_uint8(dev, "manufacturer_id", manf_id);
> qdev_prop_set_uint8(dev, "chip_id", chip_id);
> if (bdrv) {
> --
> 1.8.4.5
>
>
Reviewed-By: Igor Mammedov <imammedo@redhat.com>
--
Regards,
Igor
next prev parent reply other threads:[~2014-02-05 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 14:30 [Qemu-devel] [PATCH] nand: Don't use qdev_create() in nand_init() Andreas Färber
2014-02-05 14:56 ` Igor Mammedov [this message]
2014-02-08 17:32 ` Andreas Färber
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=20140205155623.772a6c35@thinkpad \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=kwolf@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).