From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/3] tools/nolibc: make all headers usable directly
Date: Thu, 24 Apr 2025 14:59:03 +0200 [thread overview]
Message-ID: <20250424125903.GE30489@1wt.eu> (raw)
In-Reply-To: <20250424-nolibc-header-check-v1-0-011576b6ed6f@linutronix.de>
Hi Thomas,
[ quick response ]
On Thu, Apr 24, 2025 at 01:48:10PM +0200, Thomas Weißschuh wrote:
> Make sure that any nolibc header can be included in any order.
> Even if nolibc.h was not pre-included already.
I've been wondering how to do this already and didn't come up with any
great solution. I think that your approach is the right one, indeed,
to include it out of the guards will force to respect ordering. That's
a great idea. I'm all for it!
Acked-by: Willy Tarreau <w@1wt.eu>
Willy
prev parent reply other threads:[~2025-04-24 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 11:48 [PATCH 0/3] tools/nolibc: make all headers usable directly Thomas Weißschuh
2025-04-24 11:48 ` [PATCH 1/3] tools/nolibc: add target to check header usability Thomas Weißschuh
2025-04-24 11:48 ` [PATCH 2/3] tools/nolibc: include nolibc.h early from all header files Thomas Weißschuh
2025-04-24 11:48 ` [PATCH 3/3] selftests/nolibc: always run nolibc header check Thomas Weißschuh
2025-04-24 12:59 ` 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=20250424125903.GE30489@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.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