From: Mark Brown <broonie@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: Add Linux specific waitpid() flags
Date: Mon, 23 Oct 2023 14:20:13 +0100 [thread overview]
Message-ID: <fc236f5a-8763-417f-8e9b-57da15d5dea3@sirena.org.uk> (raw)
In-Reply-To: <ZTOWQnFwrQufHUyw@1wt.eu>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Sat, Oct 21, 2023 at 11:13:38AM +0200, Willy Tarreau wrote:
> On Sat, Oct 21, 2023 at 11:00:20AM +0200, Thomas Weißschuh wrote:
> > Oct 20, 2023 23:57:01 Mark Brown <broonie@kernel.org>:
> > > Linux defines a few custom flags for waitpid(), make them available to
> > > nolibc based programs.
> > Wouldn't it be easier to include linux/wait.h instead?
> That's indeed the trend we should follow whenever possible. We've got
> caught a few times in the past with build errors depending on the
> includes ordering due to such redefinitions. I don't know if that's the
> case for these ones (nor if including linux/wait.h would cause other
> breakage) but it's worth considering at least.
> The difficulty here is that originally nolibc did not *explicitly* depend
> on UAPI headers, and was supposed to be self-sufficient (that was the
> main point). Adapting to multiple archs caused the addition of ifdefs
> all around, then trying to standardize the include file names instead
> of just "nolibc.h" caused conflicts with programs already including
> linux/anything.h. Anyway now we depend on linux/lots-of-stuff so I
> think it's worth continuing in that direction so that we don't replicate
> the UAPI maintenance effort.
OK, I'll do that - I'd not noticed that nolibc had started pulling in
linux/ headers so was trying to maintain the deliberate duplication.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-10-23 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 21:56 Mark Brown
2023-10-21 9:00 ` Thomas Weißschuh
2023-10-21 9:13 ` Willy Tarreau
2023-10-23 13:20 ` Mark Brown [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=fc236f5a-8763-417f-8e9b-57da15d5dea3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=thomas@t-8ch.de \
--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®