From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] tools/nolibc: move FD_* definitions to sys/select.h
Date: Sun, 22 Jun 2025 21:58:52 +0200 [thread overview]
Message-ID: <07f5fdb4-2c5c-4723-b12a-abdb0c9f33b7@t-8ch.de> (raw)
In-Reply-To: <20250622071958.GA3384@1wt.eu>
On 2025-06-22 09:19:58+0200, Willy Tarreau wrote:
> Hi Thomas,
>
> On Sat, Jun 21, 2025 at 10:21:47AM +0200, Thomas Weißschuh wrote:
> > On 2025-06-20 12:02:50+0200, Willy Tarreau wrote:
> > > Modern programs tend to include sys/select.h to get FD_SET() and
> > > FD_CLR() definitions as well as struct fd_set, but in our case it
> > > didn't exist. Let's move these definitions from types.h to sys/select.h
> > > to help port existing programs.
> > >
> > > Signed-off-by: Willy Tarreau <w@1wt.eu>
> >
> > <snip>
> >
> > > diff --git a/tools/include/nolibc/types.h b/tools/include/nolibc/types.h
> > > index 16c6e9ec9451f..0b51ede4e0a9c 100644
> > > --- a/tools/include/nolibc/types.h
> > > +++ b/tools/include/nolibc/types.h
> > > @@ -10,6 +10,7 @@
> > > #ifndef _NOLIBC_TYPES_H
> > > #define _NOLIBC_TYPES_H
> > >
> > > +#include "sys/select.h"
> >
> > Is this really necessary?
>
> Not sure what you mean. Do you mean that you would have preferred it
> to be included from nolibc.h instead (which I'm equally fine with) or
> that you'd prefer to have an empty sys/select.h ?
The former.
next prev parent reply other threads:[~2025-06-22 19:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:02 [PATCH 0/4] tools/nolibc: assorted fixes and small updates Willy Tarreau
2025-06-20 10:02 ` [PATCH 1/4] tools/nolibc: fix misleading help message regarding installation path Willy Tarreau
2025-06-20 10:02 ` [PATCH 2/4] tools/nolibc: add the more portable inttypes.h Willy Tarreau
2025-06-20 10:02 ` [PATCH 3/4] tools/nolibc: move FD_* definitions to sys/select.h Willy Tarreau
2025-06-21 8:21 ` Thomas Weißschuh
2025-06-22 7:19 ` Willy Tarreau
2025-06-22 19:58 ` Thomas Weißschuh [this message]
2025-06-23 2:56 ` Willy Tarreau
2025-06-29 8:46 ` Willy Tarreau
2025-06-29 8:53 ` Thomas Weißschuh
2025-06-29 9:25 ` Willy Tarreau
2025-06-29 9:37 ` Thomas Weißschuh
2025-06-29 9:40 ` Willy Tarreau
2025-06-29 15:10 ` Willy Tarreau
2025-06-29 15:54 ` Thomas Weißschuh
2025-06-29 16:08 ` Willy Tarreau
2025-06-29 16:14 ` Thomas Weißschuh
2025-06-29 16:19 ` Willy Tarreau
2025-06-29 16:27 ` Thomas Weißschuh
2025-06-29 17:56 ` Willy Tarreau
2025-06-20 10:02 ` [PATCH 4/4] tools/nolibc: add missing memchr() to string.h Willy Tarreau
2025-06-21 8:27 ` Thomas Weißschuh
2025-06-21 8:42 ` Willy Tarreau
2025-06-22 19:56 ` Thomas Weißschuh
2025-06-23 3:01 ` Willy Tarreau
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=07f5fdb4-2c5c-4723-b12a-abdb0c9f33b7@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.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®