From: Markus Armbruster <armbru@redhat.com>
To: inspireMeNow <inspiremenow@murena.io>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] fix: correct typo in ext_zvkb configuration variable Signed-off-by: Kaiyao Duan <inspiremenow@murena.io>
Date: Mon, 13 May 2024 09:24:35 +0200 [thread overview]
Message-ID: <87pltqb2do.fsf@pond.sub.org> (raw)
In-Reply-To: <20240510034747.116408-1-inspiremenow@murena.io> (inspiremenow@murena.io's message of "Fri, 10 May 2024 11:47:42 +0800")
inspireMeNow <inspiremenow@murena.io> writes:
> ---
> target/riscv/cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> index eb1a2e7d6d..13cd34adbd 100644
> --- a/target/riscv/cpu.c
> +++ b/target/riscv/cpu.c
> @@ -1535,7 +1535,7 @@ const RISCVCPUMultiExtConfig riscv_cpu_extensions[] = {
> /* Vector cryptography extensions */
> MULTI_EXT_CFG_BOOL("zvbb", ext_zvbb, false),
> MULTI_EXT_CFG_BOOL("zvbc", ext_zvbc, false),
> - MULTI_EXT_CFG_BOOL("zvkb", ext_zvkg, false),
> + MULTI_EXT_CFG_BOOL("zvkb", ext_zvkb, false),
> MULTI_EXT_CFG_BOOL("zvkg", ext_zvkg, false),
> MULTI_EXT_CFG_BOOL("zvkned", ext_zvkned, false),
> MULTI_EXT_CFG_BOOL("zvknha", ext_zvknha, false),
Commit message should be like
target/riscv: Correct definition of extension "zvkb"
Extension "zvkb" accidentally controls "zvkg" instead. [Brief
description of the bug's impact]
Fixes: ea61ef7097d0 (target/riscv: Move vector crypto extensions to riscv_cpu_extensions)
Signed-off-by: Kaiyao Duan <inspiremenow@murena.io>
Thanks!
prev parent reply other threads:[~2024-05-13 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 3:47 [PATCH] fix: correct typo in ext_zvkb configuration variable Signed-off-by: Kaiyao Duan <inspiremenow@murena.io> inspireMeNow
2024-05-13 7:24 ` Markus Armbruster [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=87pltqb2do.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=inspiremenow@murena.io \
--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).