From: Heiko Stuebner <heiko@sntech.de>
To: palmer@rivosinc.com
Cc: conor@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, christoph.muellner@vrull.eu,
ajones@ventanamicro.com, Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: [PATCH 0/2] Small fixups for the Zbb string functions
Date: Wed, 8 Feb 2023 23:53:26 +0100 [thread overview]
Message-ID: <20230208225328.1636017-1-heiko@sntech.de> (raw)
From: Heiko Stuebner <heiko.stuebner@vrull.eu>
I didn't manage to address Andrews comments on v5 [0] in time
before the series got applied, so here are two addon comments
that hopefully do his comments justice now.
[0] https://lore.kernel.org/r/20230117122447.y6tdsmsxqdwf76ri@orel
Heiko Stuebner (2):
RISC-V: fix ordering of Zbb extension
RISC-V: improve string-function assembly
arch/riscv/kernel/cpu.c | 2 +-
arch/riscv/lib/strcmp.S | 6 ++++--
arch/riscv/lib/strlen.S | 10 +++++-----
arch/riscv/lib/strncmp.S | 16 +++++++---------
4 files changed, 17 insertions(+), 17 deletions(-)
--
2.39.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-02-08 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 22:53 Heiko Stuebner [this message]
2023-02-08 22:53 ` [PATCH 1/2] RISC-V: fix ordering of Zbb extension Heiko Stuebner
2023-02-08 23:20 ` Conor Dooley
2023-02-08 23:26 ` Heiko Stübner
2023-02-09 8:25 ` Andrew Jones
2023-02-09 9:03 ` Conor Dooley
2023-02-09 9:28 ` Andrew Jones
2023-02-09 8:23 ` Andrew Jones
2023-02-08 22:53 ` [PATCH 2/2] RISC-V: improve string-function assembly Heiko Stuebner
2023-02-09 8:25 ` Andrew Jones
2023-02-10 20:49 ` [PATCH 0/2] Small fixups for the Zbb string functions Conor Dooley
2023-02-22 15:00 ` patchwork-bot+linux-riscv
2023-02-28 20:51 ` (subset) " Palmer Dabbelt
2023-02-28 21:11 ` 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=20230208225328.1636017-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=ajones@ventanamicro.com \
--cc=christoph.muellner@vrull.eu \
--cc=conor@kernel.org \
--cc=heiko.stuebner@vrull.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.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