From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Willy Tarreau" <w@1wt.eu>, "Shuah Khan" <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] tools/nolibc: add support for [v]sscanf()
Date: Wed, 31 Jul 2024 16:56:28 -0600 [thread overview]
Message-ID: <24794ab4-d22f-41ae-bb1c-83175835e509@linuxfoundation.org> (raw)
In-Reply-To: <20240731-nolibc-scanf-v1-0-f71bcc4abb9e@weissschuh.net>
On 7/31/24 12:32, Thomas Weißschuh wrote:
> The implementation is limited and only supports numeric arguments.
It would help to add more details on why this is needed especially
in the commit log.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (2):
> tools/nolibc: add support for [v]sscanf()
> Revert "selftests: kselftest: Fix build failure with NOLIBC"
>
> tools/include/nolibc/stdio.h | 93 ++++++++++++++++++++++++++++
> tools/testing/selftests/kselftest.h | 5 --
> tools/testing/selftests/nolibc/nolibc-test.c | 59 ++++++++++++++++++
> 3 files changed, 152 insertions(+), 5 deletions(-)
> ---
> base-commit: ae1f550efc11eaf1496c431d9c6e784cb49124c5
> change-id: 20240414-nolibc-scanf-f1db6930d0c6
>
> Best regards,
prev parent reply other threads:[~2024-07-31 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 18:32 [PATCH 0/2] tools/nolibc: add support for [v]sscanf() Thomas Weißschuh
2024-07-31 18:32 ` [PATCH 1/2] " Thomas Weißschuh
2024-07-31 23:01 ` Shuah Khan
2024-08-02 15:48 ` Thomas Weißschuh
2024-08-02 21:20 ` Shuah Khan
2024-08-03 10:16 ` Willy Tarreau
2024-07-31 18:32 ` [PATCH 2/2] Revert "selftests: kselftest: Fix build failure with NOLIBC" Thomas Weißschuh
2024-07-31 22:56 ` Shuah Khan [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=24794ab4-d22f-41ae-bb1c-83175835e509@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--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