From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Zhangjin Wu <falcon@tinylab.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: nolibc patches, still possible for 6.5 ?
Date: Tue, 6 Jun 2023 06:48:44 +0200 [thread overview]
Message-ID: <ZH66rI847lA1q3gq@1wt.eu> (raw)
In-Reply-To: <1fc53bcf-f7ec-4d74-a984-da4ee38e938f@t-8ch.de>
On Mon, Jun 05, 2023 at 12:44:03PM +0200, Thomas Weißschuh wrote:
> (Talking about 20230605-nolibc-rv32+stkp7,
> but the same issue is in stkp6)
>
> I noticed that the commit introducing prctl() comes *after* the one
> making use of it.
>
> 8389cb4b55ae ("selftests/nolibc: prevent coredumps during test execution")
> 033c01b5a8f4 ("tools/nolibc: add support for prctl()")
>
> This can lead to compiler errors and break bisectability.
>
> They just need to be swapped.
just done in 20230606-nolibc-rv32+stkp7a, thank you!
Willy
prev parent reply other threads:[~2023-06-06 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 13:20 nolibc patches, still possible for 6.5 ? Willy Tarreau
2023-06-04 22:57 ` Paul E. McKenney
2023-06-05 3:26 ` Willy Tarreau
2023-06-07 21:03 ` Paul E. McKenney
2023-06-07 21:22 ` Willy Tarreau
2023-06-07 23:06 ` Paul E. McKenney
2023-06-08 4:32 ` Willy Tarreau
2023-06-08 16:37 ` Paul E. McKenney
2023-06-07 21:19 ` Willy Tarreau
2023-06-07 22:58 ` Paul E. McKenney
2023-06-08 4:36 ` Willy Tarreau
2023-06-08 16:39 ` Paul E. McKenney
2023-06-08 8:13 ` Zhangjin Wu
2023-06-08 8:21 ` Willy Tarreau
2023-06-08 16:40 ` Paul E. McKenney
2023-06-05 10:44 ` Thomas Weißschuh
2023-06-06 4:48 ` Willy Tarreau [this message]
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=ZH66rI847lA1q3gq@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=thomas@t-8ch.de \
/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