From: Paul Walmsley <pjw@kernel.org>
To: Hui Wang <hui.wang@canonical.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: [PATCH] riscv: cpufeature: Drop this_hwcap clear in T-Head vector workaround
Date: Thu, 30 Apr 2026 14:08:46 -0600 (MDT) [thread overview]
Message-ID: <5d71ef6a-ef04-571f-9258-b7727f649ad5@kernel.org> (raw)
In-Reply-To: <20260430045350.22213-1-hui.wang@canonical.com>
On Thu, 30 Apr 2026, Hui Wang wrote:
> The variable this_hwcap is initialized to 0 for each loop, it is not
> necessary to do the bit clearance since this_hwcap is still 0 at this
> point, clearing the source_isa is enough here.
>
> Signed-off-by: Hui Wang <hui.wang@canonical.com>
Thanks, queued for v7.1-rc.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-04-30 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 4:53 [PATCH] riscv: cpufeature: Drop this_hwcap clear in T-Head vector workaround Hui Wang
2026-04-30 20:08 ` Paul Walmsley [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=5d71ef6a-ef04-571f-9258-b7727f649ad5@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=hui.wang@canonical.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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