From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Feng Jiang <jiangfeng@kylinos.cn>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, akpm@linux-foundation.org, kees@kernel.org,
andy@kernel.org, ebiggers@kernel.org, martin.petersen@oracle.com,
ardb@kernel.org, charlie@rivosinc.com,
conor.dooley@microchip.com, ajones@ventanamicro.com,
linus.walleij@linaro.org, nathan@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH v3 1/8] lib/string_kunit: add correctness test for strlen
Date: Tue, 20 Jan 2026 09:28:53 +0200 [thread overview]
Message-ID: <aW8utSeRsKSD8kg5@smile.fi.intel.com> (raw)
In-Reply-To: <20260120065852.166857-2-jiangfeng@kylinos.cn>
On Tue, Jan 20, 2026 at 02:58:45PM +0800, Feng Jiang wrote:
> Add a KUnit test for strlen() to verify correctness across
> different string lengths and memory alignments.
Acked-by: Andy Shevchenko <andy@kernel.org>
--
With Best Regards,
Andy Shevchenko
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-01-20 7:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:58 [PATCH v3 0/8] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-20 6:58 ` [PATCH v3 1/8] lib/string_kunit: add correctness test for strlen Feng Jiang
2026-01-20 7:28 ` Andy Shevchenko [this message]
2026-01-20 6:58 ` [PATCH v3 2/8] lib/string_kunit: add correctness test for strnlen Feng Jiang
2026-01-20 7:29 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 3/8] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-20 7:30 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 4/8] lib/string_kunit: add performance benchmarks for strlen Feng Jiang
2026-01-20 7:46 ` Andy Shevchenko
2026-01-21 5:45 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 5/8] lib/string_kunit: extend benchmarks to strnlen and chr searches Feng Jiang
2026-01-20 7:48 ` Andy Shevchenko
2026-01-21 5:48 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 6/8] riscv: lib: add strnlen implementation Feng Jiang
2026-01-20 7:31 ` Andy Shevchenko
2026-01-21 5:52 ` Feng Jiang
2026-01-21 7:24 ` Qingfang Deng
2026-01-23 1:28 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 7/8] riscv: lib: add strchr implementation Feng Jiang
2026-01-20 7:31 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 8/8] riscv: lib: add strrchr implementation Feng Jiang
2026-01-20 7:32 ` Andy Shevchenko
2026-01-20 7:36 ` [PATCH v3 0/8] riscv: optimize string functions and add kunit tests Andy Shevchenko
2026-01-21 6:44 ` Feng Jiang
2026-01-21 7:01 ` Andy Shevchenko
2026-01-21 8:12 ` Feng Jiang
2026-01-21 10:57 ` David Laight
2026-01-23 3:12 ` Feng Jiang
2026-01-23 10:16 ` David Laight
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=aW8utSeRsKSD8kg5@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=andy@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=ebiggers@kernel.org \
--cc=jiangfeng@kylinos.cn \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
/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