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, arnd@arndb.de,
geert@linux-m68k.org, haicheng.li@intel.com,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Avoid code duplication with generic bitops implementation
Date: Thu, 25 Jan 2024 21:30:29 +0000 [thread overview]
Message-ID: <170621822925.6239.5198530018567200745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231112094421.4014931-1-xiao.w.wang@intel.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 12 Nov 2023 17:44:21 +0800 you wrote:
> There's code duplication between the fallback implementation for bitops
> __ffs/__fls/ffs/fls API and the generic C implementation in
> include/asm-generic/bitops/. To avoid this duplication, this patch renames
> the generic C implementation by adding a "generic_" prefix to them, then we
> can use these generic APIs as fallback.
>
> Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
>
> [...]
Here is the summary with links:
- riscv: Avoid code duplication with generic bitops implementation
https://git.kernel.org/riscv/c/cb4ede926134
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:[~2024-01-25 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 9:44 [PATCH] riscv: Avoid code duplication with generic bitops implementation Xiao Wang
2023-12-01 5:44 ` Charlie Jenkins
2024-01-25 21:30 ` 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=170621822925.6239.5198530018567200745.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Wang@ci.codeaurora.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=haicheng.li@intel.com \
--cc=linux-arch@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 \
/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