From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 0/3] tools/nolibc: add testcases for vfprintf
Date: Tue, 28 Mar 2023 21:01:28 +0000 [thread overview]
Message-ID: <20230328-nolibc-printf-test-v1-0-d7290ec893dd@weissschuh.net> (raw)
vfprintf() is complex and so far did not have proper tests.
This series is based on the "dev" branch of the RCU tree.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Thomas Weißschuh (3):
tools/nolibc: add wrapper for memfd_create
tools/nolibc: let FILE streams contain an fd
tools/nolibc: add testcases for vfprintf
tools/include/nolibc/stdio.h | 36 +++----------
tools/include/nolibc/sys.h | 23 +++++++++
tools/testing/selftests/nolibc/nolibc-test.c | 77 ++++++++++++++++++++++++++++
3 files changed, 107 insertions(+), 29 deletions(-)
---
base-commit: a5333c037de823912dd20e933785c63de7679e64
change-id: 20230328-nolibc-printf-test-052d5abc2118
Best regards,
--
Thomas Weißschuh <linux@weissschuh.net>
next reply other threads:[~2023-03-28 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:01 Thomas Weißschuh [this message]
2023-03-28 21:01 ` [PATCH 1/3] tools/nolibc: add wrapper for memfd_create Thomas Weißschuh
2023-03-28 21:01 ` [PATCH 2/3] tools/nolibc: let FILE streams contain an fd Thomas Weißschuh
2023-04-02 7:45 ` Willy Tarreau
2023-04-02 12:11 ` Thomas Weißschuh
2023-03-28 21:01 ` [PATCH 3/3] tools/nolibc: add testcases for vfprintf Thomas Weißschuh
2023-04-02 7:51 ` Willy Tarreau
2023-04-02 12:18 ` Thomas Weißschuh
2023-04-02 12:31 ` Willy Tarreau
2023-04-02 8:00 ` Willy Tarreau
2023-04-02 12:18 ` 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=20230328-nolibc-printf-test-v1-0-d7290ec893dd@weissschuh.net \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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;
as well as URLs for NNTP newsgroup(s).