From: Thomas Huth <thuth@redhat.com>
To: Gan Qixin <ganqixin@huawei.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
zhang.zhanghailiang@huawei.com, mst@redhat.com,
laurent@vivier.eu, armbru@redhat.com,
qemu-arm <qemu-arm@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>,
kuhn.chenqun@huawei.com, philmd@redhat.com
Subject: Re: [PATCH v2 1/4] ssd0323: put it into the 'display' category
Date: Thu, 12 Nov 2020 08:34:28 +0100 [thread overview]
Message-ID: <a9bffd4f-973f-2c35-58f2-7d0d6967c4ca@redhat.com> (raw)
In-Reply-To: <20201111164710.644863-2-ganqixin@huawei.com>
On 11/11/2020 17.47, Gan Qixin wrote:
> The category of the ssd0323 device is not set, put it into the 'display'
> category.
>
> Signed-off-by: Gan Qixin <ganqixin@huawei.com>
> ---
> hw/display/ssd0323.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/display/ssd0323.c b/hw/display/ssd0323.c
> index 17d4b32ae3..cbfd21dfd5 100644
> --- a/hw/display/ssd0323.c
> +++ b/hw/display/ssd0323.c
> @@ -370,6 +370,7 @@ static void ssd0323_class_init(ObjectClass *klass, void *data)
> k->transfer = ssd0323_transfer;
> k->cs_polarity = SSI_CS_HIGH;
> dc->vmsd = &vmstate_ssd0323;
> + set_bit(DEVICE_CATEGORY_DISPLAY, dc->categories);
> }
>
> static const TypeInfo ssd0323_info = {
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-11-12 7:38 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 [this message]
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
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=a9bffd4f-973f-2c35-58f2-7d0d6967c4ca@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=ganqixin@huawei.com \
--cc=kraxel@redhat.com \
--cc=kuhn.chenqun@huawei.com \
--cc=laurent@vivier.eu \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@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).