From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Shuah Khan" <shuah@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: nolibc changes since 6.6-rc1 for linux-next
Date: Thu, 5 Oct 2023 14:15:31 -0600 [thread overview]
Message-ID: <dcfa99da-eb3e-4c85-9e7f-092bbb1be801@linuxfoundation.org> (raw)
In-Reply-To: <11a790c0-f9c0-49eb-b14f-56b962af6d2d@t-8ch.de>
Hi Thomas,
On 10/5/23 11:00, Thomas Weißschuh wrote:
> Hi Shuah,
>
> I'd like to test the current state of nolibc in linux-next.
> Could pull the request below into your nolibc branch?
>
> I'll do some manual tests this weekend, too.
>
>
> Thanks,
> Thomas
>
>
> The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
>
> Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git nolibc/next
>
> for you to fetch changes up to ab663cc32912914258bc8a2fbd0e753f552ee9d8:
>
> tools/nolibc: automatically detect necessity to use pselect6 (2023-09-28 09:20:35 +0200)
Absolutely. Do you mind tagging and pushing the tag and send
pull request with the tag?
thanks,
-- Shuah
next prev parent reply other threads:[~2023-10-05 20:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 17:00 Thomas Weißschuh
2023-10-05 20:15 ` Shuah Khan [this message]
2023-10-05 20:28 ` Thomas Weißschuh
2023-10-05 20:58 ` Paul E. McKenney
2023-10-05 21:30 ` Shuah Khan
2023-10-06 0:01 ` Paul E. McKenney
2023-10-07 7:06 ` Willy Tarreau
2023-10-07 15:42 ` Paul E. McKenney
2023-10-08 12:58 ` Thomas Weißschuh
2023-10-08 16:27 ` Paul E. McKenney
2023-10-09 6:53 ` Willy Tarreau
2023-10-09 7:22 ` Thomas Weißschuh
2023-10-09 7:30 ` Willy Tarreau
2023-10-09 13:54 ` Paul E. McKenney
2023-10-09 11:25 ` Thomas Weißschuh
2023-10-09 12:02 ` Willy Tarreau
2023-10-09 16:18 ` 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=dcfa99da-eb3e-4c85-9e7f-092bbb1be801@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@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
Powered by JetHome