From: Andrew Jones <ajones@ventanamicro.com>
To: Chin Yik Ming <yikming2222@gmail.com>
Cc: conor@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, charlie@rivosinc.com,
samuel.holland@sifive.com, cleger@rivosinc.com,
andybnac@gmail.com, alexghiti@rivosinc.com,
peterlin@andestech.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Simplify base extension checks and direct boolean return
Date: Thu, 30 Jan 2025 09:50:20 +0100 [thread overview]
Message-ID: <20250130-77bf6cf799f468b43fb5382e@orel> (raw)
In-Reply-To: <20250129203843.1136838-1-yikming2222@gmail.com>
On Thu, Jan 30, 2025 at 04:38:43AM +0800, Chin Yik Ming wrote:
> Reduce three lines checking to single line using a ternary conditional
> expression for getting the base extension word. In addition, the
> test_bit macro function already return a boolean which matches the
> return type of the caller, so directly return the result of the test_bit
> macro function.
>
> Signed-off-by: Chin Yik Ming <yikming2222@gmail.com>
> ---
> arch/riscv/kernel/cpufeature.c | 6 ++----
> arch/riscv/kernel/vendor_extensions.c | 2 +-
> 2 files changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/arch/riscv/kernel/cpufeature.c b/arch/riscv/kernel/cpufeature.c
> index c0916ed318c2..32525b69ab99 100644
> --- a/arch/riscv/kernel/cpufeature.c
> +++ b/arch/riscv/kernel/cpufeature.c
> @@ -49,9 +49,7 @@ struct riscv_isainfo hart_isa[NR_CPUS];
> */
> unsigned long riscv_isa_extension_base(const unsigned long *isa_bitmap)
> {
> - if (!isa_bitmap)
> - return riscv_isa[0];
> - return isa_bitmap[0];
> + return !isa_bitmap ? riscv_isa[0] : isa_bitmap[0];
> }
> EXPORT_SYMBOL_GPL(riscv_isa_extension_base);
>
> @@ -72,7 +70,7 @@ bool __riscv_isa_extension_available(const unsigned long *isa_bitmap, unsigned i
> if (bit >= RISCV_ISA_EXT_MAX)
> return false;
>
> - return test_bit(bit, bmap) ? true : false;
> + return test_bit(bit, bmap);
> }
> EXPORT_SYMBOL_GPL(__riscv_isa_extension_available);
>
> diff --git a/arch/riscv/kernel/vendor_extensions.c b/arch/riscv/kernel/vendor_extensions.c
> index a8126d118341..62f55bc779e9 100644
> --- a/arch/riscv/kernel/vendor_extensions.c
> +++ b/arch/riscv/kernel/vendor_extensions.c
> @@ -51,6 +51,6 @@ bool __riscv_isa_vendor_extension_available(int cpu, unsigned long vendor, unsig
> if (bit >= RISCV_ISA_VENDOR_EXT_MAX)
> return false;
>
> - return test_bit(bit, bmap->isa) ? true : false;
> + return test_bit(bit, bmap->isa);
> }
> EXPORT_SYMBOL_GPL(__riscv_isa_vendor_extension_available);
> --
> 2.34.1
>
Since the changes are harmless and I do prefer the way the code looks
with them,
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
but these types of changes are pretty much just pointless churn...
Thanks,
drew
next prev parent reply other threads:[~2025-01-30 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 20:38 [PATCH] riscv: Simplify base extension checks and direct boolean return Chin Yik Ming
2025-01-30 8:50 ` Andrew Jones [this message]
2025-03-27 3:24 ` patchwork-bot+linux-riscv
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=20250130-77bf6cf799f468b43fb5382e@orel \
--to=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=samuel.holland@sifive.com \
--cc=yikming2222@gmail.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