qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Gan Qixin <ganqixin@huawei.com>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: zhang.zhanghailiang@huawei.com,
	Qemu-block <qemu-block@nongnu.org>,
	laurent@vivier.eu, armbru@redhat.com, kuhn.chenqun@huawei.com,
	philmd@redhat.com
Subject: Re: [PATCH v2 3/4] nand: put it into the 'storage' category
Date: Thu, 12 Nov 2020 08:38:41 +0100	[thread overview]
Message-ID: <4942269b-86bd-ce1b-eeaa-bebe27a4f0fb@redhat.com> (raw)
In-Reply-To: <20201111164710.644863-4-ganqixin@huawei.com>

On 11/11/2020 17.47, Gan Qixin wrote:
> The category of the nand device is not set, put it into the 'storage'
> category.
> 
> Signed-off-by: Gan Qixin <ganqixin@huawei.com>
> ---
>  hw/block/nand.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/hw/block/nand.c b/hw/block/nand.c
> index bcceb64ebb..1d7a48a2ec 100644
> --- a/hw/block/nand.c
> +++ b/hw/block/nand.c
> @@ -449,6 +449,7 @@ static void nand_class_init(ObjectClass *klass, void *data)
>      dc->reset = nand_reset;
>      dc->vmsd = &vmstate_nand;
>      device_class_set_props(dc, nand_properties);
> +    set_bit(DEVICE_CATEGORY_STORAGE, dc->categories);
>  }
>  
>  static const TypeInfo nand_info = {
> 

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2020-11-12  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 16:47 [PATCH v2 0/4] Categorize some uncategorized devices Gan Qixin
2020-11-11 16:47 ` [PATCH v2 1/4] ssd0323: put it into the 'display' category Gan Qixin
2020-11-12  7:34   ` Thomas Huth
2020-11-11 16:47 ` [PATCH v2 2/4] ads7846: " Gan Qixin
2020-11-12  7:36   ` Thomas Huth
2020-11-12 11:19   ` Peter Maydell
2020-11-12 11:53     ` ganqixin
2020-11-11 16:47 ` [PATCH v2 3/4] nand: put it into the 'storage' category Gan Qixin
2020-11-12  7:38   ` Thomas Huth [this message]
2020-11-11 16:47 ` [PATCH v2 4/4] max111x: put it into the 'misc' category Gan Qixin

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=4942269b-86bd-ce1b-eeaa-bebe27a4f0fb@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ganqixin@huawei.com \
    --cc=kuhn.chenqun@huawei.com \
    --cc=laurent@vivier.eu \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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).