From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, alex.bennee@linaro.org,
akihiko.odaki@daynix.com
Subject: Re: [PATCH v2 0/1] riscv, gdbstub.c: fix reg_width in ricsv_gen_dynamic_vector_feature()
Date: Mon, 27 May 2024 15:17:46 +1000 [thread overview]
Message-ID: <CAKmqyKPxPcUFTbERAgaB6TbyfLoM21Gfq56ks2qj7JeuQM_aRQ@mail.gmail.com> (raw)
In-Reply-To: <20240517203054.880861-1-dbarboza@ventanamicro.com>
On Sat, May 18, 2024 at 6:32 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> In this v2 'reg_width' was renamed to 'bitsize' to provide a bit more
> clarity about what's the value type of the variable. It is the same name
> used by riscv_gen_dynamic_csr_feature() for a variable that has the same
> purpose. The variable rename was suggested by Alex in v1.
>
> Changes from v1:
> - rename 'reg_width' to 'bitsize'
> - v1 link: https://lore.kernel.org/qemu-riscv/20240516171010.639591-1-dbarboza@ventanamicro.com/
>
> Daniel Henrique Barboza (1):
> riscv, gdbstub.c: fix reg_width in ricsv_gen_dynamic_vector_feature()
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> target/riscv/gdbstub.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --
> 2.44.0
>
>
prev parent reply other threads:[~2024-05-27 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 20:30 [PATCH v2 0/1] riscv, gdbstub.c: fix reg_width in ricsv_gen_dynamic_vector_feature() Daniel Henrique Barboza
2024-05-17 20:30 ` [PATCH v2 1/1] " Daniel Henrique Barboza
2024-05-18 6:57 ` Akihiko Odaki
2024-05-27 5:14 ` Alistair Francis
2024-05-27 5:17 ` Alistair Francis [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=CAKmqyKPxPcUFTbERAgaB6TbyfLoM21Gfq56ks2qj7JeuQM_aRQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).