From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com, w@1wt.eu,
alviro.iskandar@gnuweeb.org, ammarfaizi2@gnuweeb.org
Subject: [GIT PULL] nolibc changes for v5.20 (or whatever)
Date: Sun, 31 Jul 2022 09:57:56 -0700 [thread overview]
Message-ID: <20220731165756.GA3034113@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
Once the merge window opens, please pull the latest nolibc changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/nolibc.2022.07.27a
# HEAD 4f8126f3a665456b68ae923cd7a7e9b9eb98547d: tools/nolibc: add a help target to list supported targets (2022-06-20 09:43:19 -0700)
----------------------------------------------------------------
nolibc pull request for v5.20 (or whatever)
This branch provides nolibc updates, perhaps most notably improved testing
via the "cd tools/include/nolibc; make headers" command. This should
be considered a smoke test. More thorough testing is in the works.
----------------------------------------------------------------
Alviro Iskandar Setiawan (1):
tools/nolibc/stdio: Add format attribute to enable printf warnings
Ammar Faizi (1):
tools/nolibc/stdlib: Support overflow checking for older compiler versions
Willy Tarreau (3):
tools/nolibc: fix the makefile to also work as "make -C tools ..."
tools/nolibc: make the default target build the headers
tools/nolibc: add a help target to list supported targets
tools/Makefile | 3 +++
tools/include/nolibc/Makefile | 37 +++++++++++++++++++++++++++++++++++--
tools/include/nolibc/stdio.h | 4 ++--
tools/include/nolibc/stdlib.h | 7 +++----
4 files changed, 43 insertions(+), 8 deletions(-)
next reply other threads:[~2022-07-31 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 16:57 Paul E. McKenney [this message]
2022-08-03 3:23 ` pr-tracker-bot
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=20220731165756.GA3034113@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®