From: Zheyu Ma <zheyuma97@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] hw/gpio/aspeed: Add reg_table_size to AspeedGPIOClass
Date: Thu, 20 Jun 2024 16:03:27 +0200 [thread overview]
Message-ID: <CAMhUBjme1Pj7k5=O9yBwABqM0kF9f29upfpJRTxZJAyz43T9Kw@mail.gmail.com> (raw)
In-Reply-To: <5d617ff8-dc3d-4126-8466-ed1596d3389d@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Thu, Jun 20, 2024 at 2:35 PM Cédric Le Goater <clg@kaod.org> wrote:
>
> >> @@ -75,6 +75,7 @@ struct AspeedGPIOClass {
> >> uint32_t nr_gpio_pins;
> >> uint32_t nr_gpio_sets;
> >> const AspeedGPIOReg *reg_table;
> >> + uint32_t reg_table_size;
> >> };
> >
> > - "reg_table_size" is a number of registers, using s/size/count/ might
> > be clearer.
> > - No point in specifying 32-bit, "unsigned" is sufficient.
> >
> > (Cédric, if you agree, you might update your tree).
> >
> > Unrelated to this patch but figured out while reviewing, in
> > aspeed_gpio_read/write 'idx' is
> > - pointlessly assigned to -1
> > - of type 'uint64_t', also pointless, 'unsigned' is clearer.
>
> Zheyu, could you please send a v4 ? Thanks,
>
Sure. I've sent it.
Zheyu
[-- Attachment #2: Type: text/html, Size: 1301 bytes --]
prev parent reply other threads:[~2024-06-20 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 18:36 [PATCH v3] hw/gpio/aspeed: Add reg_table_size to AspeedGPIOClass Zheyu Ma
2024-06-19 23:48 ` Andrew Jeffery
2024-06-20 5:44 ` Cédric Le Goater
2024-06-20 11:09 ` Philippe Mathieu-Daudé
2024-06-20 12:35 ` Cédric Le Goater
2024-06-20 14:03 ` Zheyu Ma [this message]
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='CAMhUBjme1Pj7k5=O9yBwABqM0kF9f29upfpJRTxZJAyz43T9Kw@mail.gmail.com' \
--to=zheyuma97@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).