From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/4] ich9: fix getter type for sci_int property
Date: Mon, 25 Nov 2019 17:43:40 +0100 [thread overview]
Message-ID: <deed1398-8b39-02b9-6da5-6d1fc4edff4b@redhat.com> (raw)
In-Reply-To: <20191125153619.39893-3-felipe@nutanix.com>
On 11/25/19 4:36 PM, Felipe Franciosi wrote:
> When QOM APIs were added to ich9 in 6f1426ab, the getter for sci_int was
> written using uint32_t. However, the object property is uint8_t. This
> fixes the getter for correctness.
>
> Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
> ---
> hw/isa/lpc_ich9.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/isa/lpc_ich9.c b/hw/isa/lpc_ich9.c
> index 5555ce3342..240979885d 100644
> --- a/hw/isa/lpc_ich9.c
> +++ b/hw/isa/lpc_ich9.c
> @@ -631,9 +631,9 @@ static void ich9_lpc_get_sci_int(Object *obj, Visitor *v, const char *name,
> void *opaque, Error **errp)
> {
> ICH9LPCState *lpc = ICH9_LPC_DEVICE(obj);
> - uint32_t value = lpc->sci_gsi;
> + uint8_t value = lpc->sci_gsi;
>
> - visit_type_uint32(v, name, &value, errp);
> + visit_type_uint8(v, name, &value, errp);
Maybe directly as:
visit_type_uint8(v, name, &lpc->sci_gsi, errp);
With/without stack variable:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> }
>
> static void ich9_lpc_add_properties(ICH9LPCState *lpc)
> @@ -641,7 +641,7 @@ static void ich9_lpc_add_properties(ICH9LPCState *lpc)
> static const uint8_t acpi_enable_cmd = ICH9_APM_ACPI_ENABLE;
> static const uint8_t acpi_disable_cmd = ICH9_APM_ACPI_DISABLE;
>
> - object_property_add(OBJECT(lpc), ACPI_PM_PROP_SCI_INT, "uint32",
> + object_property_add(OBJECT(lpc), ACPI_PM_PROP_SCI_INT, "uint8",
> ich9_lpc_get_sci_int,
> NULL, NULL, NULL, NULL);
> object_property_add_uint8_ptr(OBJECT(lpc), ACPI_PM_PROP_ACPI_ENABLE_CMD,
>
next prev parent reply other threads:[~2019-11-25 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 15:36 [PATCH 0/4] Improve default object property_add uint helpers Felipe Franciosi
2019-11-25 15:36 ` [PATCH 1/4] qom/object: enable setter for uint types Felipe Franciosi
2019-11-26 8:40 ` Marc-André Lureau
2019-11-26 12:03 ` Felipe Franciosi
2019-11-26 12:18 ` Marc-André Lureau
2019-11-26 13:41 ` Felipe Franciosi
2019-11-25 15:36 ` [PATCH 2/4] ich9: fix getter type for sci_int property Felipe Franciosi
2019-11-25 16:43 ` Philippe Mathieu-Daudé [this message]
2019-11-26 9:55 ` Felipe Franciosi
2019-11-26 8:40 ` Marc-André Lureau
2019-11-25 15:36 ` [PATCH 3/4] ich9: Simplify ich9_lpc_initfn Felipe Franciosi
2019-11-26 8:39 ` Marc-André Lureau
2019-11-25 15:36 ` [PATCH 4/4] qom/object: Use common get/set uint helpers Felipe Franciosi
2019-11-26 8:39 ` Marc-André Lureau
2019-11-26 9:39 ` Felipe Franciosi
2019-11-27 23:58 ` Alexey Kardashevskiy
2019-11-28 16:12 ` Felipe Franciosi
-- strict thread matches above, loose matches on Subject: below --
2020-02-03 15:54 [PATCH 0/4] Improve default object property_add " Felipe Franciosi
2020-02-03 15:54 ` [PATCH 2/4] ich9: fix getter type for sci_int property Felipe Franciosi
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=deed1398-8b39-02b9-6da5-6d1fc4edff4b@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=felipe@nutanix.com \
--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).