From: patchwork-bot+linux-riscv@kernel.org
To: Chin Yik Ming <yikming2222@gmail.com>
Cc: linux-riscv@lists.infradead.org, conor@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, charlie@rivosinc.com,
ajones@ventanamicro.com, samuel.holland@sifive.com,
cleger@rivosinc.com, andybnac@gmail.com, alexghiti@rivosinc.com,
peterlin@andestech.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Simplify base extension checks and direct boolean return
Date: Thu, 27 Mar 2025 03:24:56 +0000 [thread overview]
Message-ID: <174304589675.1549280.4837326210822178054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250129203843.1136838-1-yikming2222@gmail.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Thu, 30 Jan 2025 04:38:43 +0800 you 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>
>
> [...]
Here is the summary with links:
- riscv: Simplify base extension checks and direct boolean return
https://git.kernel.org/riscv/c/7f238b12660e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-27 3:24 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
2025-03-27 3:24 ` patchwork-bot+linux-riscv [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=174304589675.1549280.4837326210822178054.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=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