mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: shuah@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] tools/nolibc: add missing memchr() to string.h
Date: Sun, 2 Nov 2025 12:10:06 +0100	[thread overview]
Message-ID: <f30441ce-66ba-4de8-94ac-98f4b17b5ef4@t-8ch.de> (raw)
In-Reply-To: <20251102104611.24454-4-w@1wt.eu>

On 2025-11-02 11:46:10+0100, Willy Tarreau wrote:
> Surprisingly we forgot to add this common one. It was added with a
> per-arch guard allowing to later implement it in arch-specific asm
> code like was done for a few other ones.
> 
> The test verifies that we don't search past the indicated length.
> 
> Signed-off-by: Willy Tarreau <w@1wt.eu>
> ---
>  tools/include/nolibc/string.h                | 15 +++++++++++++++
>  tools/testing/selftests/nolibc/nolibc-test.c |  2 ++
>  2 files changed, 17 insertions(+)

Applied.

  reply	other threads:[~2025-11-02 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02 10:46 [PATCH v2 0/4] tools/nolibc: assorted fixes and small updates Willy Tarreau
2025-11-02 10:46 ` [PATCH v2 1/4] tools/nolibc: fix misleading help message regarding installation path Willy Tarreau
2025-11-02 11:03   ` Thomas Weißschuh
2025-11-02 10:46 ` [PATCH v2 2/4] tools/nolibc: add the more portable inttypes.h Willy Tarreau
2025-11-02 11:04   ` Thomas Weißschuh
2025-11-02 11:18     ` Willy Tarreau
2025-11-02 11:41       ` Thomas Weißschuh
2025-11-02 10:46 ` [PATCH v2 3/4] tools/nolibc: add missing memchr() to string.h Willy Tarreau
2025-11-02 11:10   ` Thomas Weißschuh [this message]
2025-11-02 10:46 ` [PATCH v2 4/4] tools/nolibc: provide the portable sys/select.h Willy Tarreau
2025-11-02 12:51   ` Thomas Weißschuh

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=f30441ce-66ba-4de8-94ac-98f4b17b5ef4@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®