From: "Paul E. McKenney" <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: [PATCH rcu 0/5] nolibc updates for v5.20
Date: Mon, 20 Jun 2022 16:13:25 -0700 [thread overview]
Message-ID: <20220620231325.GA3845036@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello!
This series provides nolibc updates, including improved testing:
1. Support overflow checking for older compiler versions, courtesy
of Ammar Faizi.
2. Add format attribute to enable printf warnings, courtesy of
Alviro Iskandar Setiawan.
3. fix the makefile to also work as "make -C tools ...", courtesy
of Willy Tarreau.
4. make the default target build the headers, courtesy of Willy
Tarreau.
5. add a help target to list supported targets, courtesy of Willy
Tarreau.
Thanx, Paul
------------------------------------------------------------------------
b/tools/Makefile | 3 +++
b/tools/include/nolibc/Makefile | 18 +++++++++++++++++-
b/tools/include/nolibc/stdio.h | 4 ++--
b/tools/include/nolibc/stdlib.h | 7 +++----
tools/include/nolibc/Makefile | 19 ++++++++++++++++++-
5 files changed, 43 insertions(+), 8 deletions(-)
next reply other threads:[~2022-06-20 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 23:13 Paul E. McKenney [this message]
2022-06-20 23:13 ` [PATCH rcu 1/5] tools/nolibc/stdlib: Support overflow checking for older compiler versions Paul E. McKenney
2022-06-20 23:13 ` [PATCH rcu 2/5] tools/nolibc/stdio: Add format attribute to enable printf warnings Paul E. McKenney
2022-06-20 23:13 ` [PATCH rcu 3/5] tools/nolibc: fix the makefile to also work as "make -C tools ..." Paul E. McKenney
2022-06-20 23:13 ` [PATCH rcu 4/5] tools/nolibc: make the default target build the headers Paul E. McKenney
2022-06-20 23:13 ` [PATCH rcu 5/5] tools/nolibc: add a help target to list supported targets Paul E. McKenney
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=20220620231325.GA3845036@paulmck-ThinkPad-P17-Gen-1 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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