From: patchwork-bot+linux-riscv@kernel.org
To: Wang@ci.codeaurora.org, Xiao W <xiao.w.wang@intel.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, ardb@kernel.org,
anup@brainfault.org, haicheng.li@intel.com,
ajones@ventanamicro.com, yujie.liu@intel.com,
charlie@rivosinc.com, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] riscv: Optimize bitops with Zbb extension
Date: Thu, 09 Nov 2023 22:40:24 +0000 [thread overview]
Message-ID: <169956962496.25145.13807826919853509041.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231031064553.2319688-1-xiao.w.wang@intel.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 31 Oct 2023 14:45:51 +0800 you wrote:
> Bitops optimization with specialized instructions is common practice in
> popular ISAs, this patch set uses RISC-V Zbb extension to optimize four
> bitops: __ffs, __fls, ffs and fls.
>
> The first patch rearranges the content in hwcap.h and cpufeature.h, it helps
> to avoid a cyclic header including issue for patch 2.
>
> [...]
Here is the summary with links:
- [v5,1/2] riscv: Rearrange hwcap.h and cpufeature.h
https://git.kernel.org/riscv/c/e72c4333d2f2
- [v5,2/2] riscv: Optimize bitops with Zbb extension
https://git.kernel.org/riscv/c/457926b25320
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
prev parent reply other threads:[~2023-11-09 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 6:45 [PATCH v5 0/2] riscv: Optimize bitops with Zbb extension Xiao Wang
2023-10-31 6:45 ` [PATCH v5 1/2] riscv: Rearrange hwcap.h and cpufeature.h Xiao Wang
2023-10-31 6:45 ` [PATCH v5 2/2] riscv: Optimize bitops with Zbb extension Xiao Wang
2023-11-10 9:24 ` Geert Uytterhoeven
2023-11-12 7:05 ` Wang, Xiao W
2023-11-09 22:40 ` 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=169956962496.25145.13807826919853509041.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Wang@ci.codeaurora.org \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=charlie@rivosinc.com \
--cc=haicheng.li@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=xiao.w.wang@intel.com \
--cc=yujie.liu@intel.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