From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
christoph.muellner@vrull.eu, heiko.stuebner@vrull.eu,
bjorn@rivosinc.com, conor.dooley@microchip.com,
linux@roeck-us.net, ajones@ventanamicro.com
Subject: Re: [PATCH] riscv, lib: Fix Zbb strncmp
Date: Wed, 01 Mar 2023 03:20:17 +0000 [thread overview]
Message-ID: <167764081777.10705.11052851950584428233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230228184211.1585641-1-bjorn@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 28 Feb 2023 19:42:10 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> The Zbb optimized strncmp has two parts; a fast path that does XLEN/8B
> per iteration, and a slow that does one byte per iteration.
>
> The idea is to compare aligned XLEN chunks for most of strings, and do
> the remainder tail in the slow path.
>
> [...]
Here is the summary with links:
- riscv, lib: Fix Zbb strncmp
https://git.kernel.org/riscv/c/81a1dd10b072
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-03-01 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 18:42 [PATCH] riscv, lib: Fix Zbb strncmp Björn Töpel
2023-02-28 19:12 ` Conor Dooley
2023-02-28 19:41 ` Björn Töpel
2023-02-28 19:53 ` Guenter Roeck
2023-02-28 21:18 ` Guenter Roeck
2023-02-28 21:55 ` Palmer Dabbelt
2023-03-01 3:20 ` 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=167764081777.10705.11052851950584428233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=conor.dooley@microchip.com \
--cc=heiko.stuebner@vrull.eu \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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