All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	yury.norov@gmail.com, linux@rasmusvillemoes.dk, pjw@kernel.org,
	charlie@rivosinc.com, xiao.w.wang@intel.com,
	christoph.muellner@vrull.eu, uwu@dram.page,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] riscv: Use riscv_has_extension_{likely,unlikely}
Date: Tue, 18 Nov 2025 08:13:53 +0000	[thread overview]
Message-ID: <176345363325.4032995.8761332342399435783.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020-riscv-altn-helper-wip-v4-0-ef941c87669a@iscas.ac.cn>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 20 Oct 2025 17:09:55 +0800 you wrote:
> There are about a dozen uses of asm goto in arch/riscv just to select
> between two code paths with the alternative mechanism. Convert them to
> the existing helpers riscv_has_extension_{likely,unlikely}.
> 
> In each case, I have preserved the existing code's choice of asm goto
> pattern while picking between "likely" and "unlikely", namely:
> 
> [...]

Here is the summary with links:
  - [v4,1/5] riscv: pgtable: Use riscv_has_extension_unlikely
    https://git.kernel.org/riscv/c/a4076db168ae
  - [v4,2/5] riscv: checksum: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/343fdc9e98d8
  - [v4,3/5] riscv: hweight: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/8211f7ec8a7f
  - [v4,4/5] riscv: bitops: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/d78307511f7c
  - [v4,5/5] riscv: cmpxchg: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/7b5a4f97cb45

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	yury.norov@gmail.com, linux@rasmusvillemoes.dk, pjw@kernel.org,
	charlie@rivosinc.com, xiao.w.wang@intel.com,
	christoph.muellner@vrull.eu, uwu@dram.page,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] riscv: Use riscv_has_extension_{likely,unlikely}
Date: Tue, 18 Nov 2025 08:13:53 +0000	[thread overview]
Message-ID: <176345363325.4032995.8761332342399435783.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020-riscv-altn-helper-wip-v4-0-ef941c87669a@iscas.ac.cn>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 20 Oct 2025 17:09:55 +0800 you wrote:
> There are about a dozen uses of asm goto in arch/riscv just to select
> between two code paths with the alternative mechanism. Convert them to
> the existing helpers riscv_has_extension_{likely,unlikely}.
> 
> In each case, I have preserved the existing code's choice of asm goto
> pattern while picking between "likely" and "unlikely", namely:
> 
> [...]

Here is the summary with links:
  - [v4,1/5] riscv: pgtable: Use riscv_has_extension_unlikely
    https://git.kernel.org/riscv/c/a4076db168ae
  - [v4,2/5] riscv: checksum: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/343fdc9e98d8
  - [v4,3/5] riscv: hweight: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/8211f7ec8a7f
  - [v4,4/5] riscv: bitops: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/d78307511f7c
  - [v4,5/5] riscv: cmpxchg: Use riscv_has_extension_likely
    https://git.kernel.org/riscv/c/7b5a4f97cb45

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-11-18  8:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  9:09 [PATCH v4 0/5] riscv: Use riscv_has_extension_{likely,unlikely} Vivian Wang
2025-10-20  9:09 ` Vivian Wang
2025-10-20  9:09 ` [PATCH v4 1/5] riscv: pgtable: Use riscv_has_extension_unlikely Vivian Wang
2025-10-20  9:09   ` Vivian Wang
2025-10-20  9:09 ` [PATCH v4 2/5] riscv: checksum: Use riscv_has_extension_likely Vivian Wang
2025-10-20  9:09   ` Vivian Wang
2025-10-20  9:09 ` [PATCH v4 3/5] riscv: hweight: " Vivian Wang
2025-10-20  9:09   ` Vivian Wang
2025-10-20  9:09 ` [PATCH v4 4/5] riscv: bitops: " Vivian Wang
2025-10-20  9:09   ` Vivian Wang
2025-10-20  9:10 ` [PATCH v4 5/5] riscv: cmpxchg: " Vivian Wang
2025-10-20  9:10   ` Vivian Wang
2025-11-18  8:13 ` patchwork-bot+linux-riscv [this message]
2025-11-18  8:13   ` [PATCH v4 0/5] riscv: Use riscv_has_extension_{likely,unlikely} 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=176345363325.4032995.8761332342399435783.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pjw@kernel.org \
    --cc=uwu@dram.page \
    --cc=wangruikang@iscas.ac.cn \
    --cc=xiao.w.wang@intel.com \
    --cc=yury.norov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.