From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <skhan@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: Addition of the nolibc tree
Date: Thu, 1 May 2025 18:30:14 +0200 [thread overview]
Message-ID: <6d906909-99ae-4934-901b-983ad7d3cbda@t-8ch.de> (raw)
Hi Stephen,
could you add the nolibc tree to linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git#for-next
It replaces the nolibc tree from Shuah.
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git#nolibc
Thanks,
Thomas
next reply other threads:[~2025-05-01 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 16:30 Thomas Weißschuh [this message]
2025-05-01 22:53 ` Stephen Rothwell
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=6d906909-99ae-4934-901b-983ad7d3cbda@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.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®