From: Conor Dooley <conor@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: palmer@rivosinc.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, christoph.muellner@vrull.eu,
ajones@ventanamicro.com, Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: Re: [PATCH 0/2] Small fixups for the Zbb string functions
Date: Fri, 10 Feb 2023 20:49:11 +0000 [thread overview]
Message-ID: <Y+atx6E2k8Ao33Zz@spud> (raw)
In-Reply-To: <20230208225328.1636017-1-heiko@sntech.de>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Wed, Feb 08, 2023 at 11:53:26PM +0100, Heiko Stuebner wrote:
> 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.
Running this on my jh7110 at the moment, so I suppose this is:
Tested-by: Conor Dooley <conor.dooley@microchip.com>
;)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-10 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 22:53 [PATCH 0/2] Small fixups for the Zbb string functions Heiko Stuebner
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 ` Conor Dooley [this message]
2023-02-22 15:00 ` [PATCH 0/2] Small fixups for the Zbb string functions 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=Y+atx6E2k8Ao33Zz@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=christoph.muellner@vrull.eu \
--cc=heiko.stuebner@vrull.eu \
--cc=heiko@sntech.de \
--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