From: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH] system_data_types.7: Add 'fd_set'
Date: Fri, 9 Oct 2020 10:42:44 +0200 [thread overview]
Message-ID: <20201009084243.8153-1-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <CAKgNAki7jWqR3tKUMKRdpK_5gvG+N1RC+sZ_GrK6QO0UvD8SGA@mail.gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
Hi Michael,
I found that POSIX defines the limit in a macro, so I used that.
Thanks,
Alex
man7/system_data_types.7 | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index b0e0d2b48..a4a2e0ab8 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -151,6 +151,28 @@ See also the
.I float_t
type in this page.
.RE
+.\"------------------------------------- fd_set -----------------------/
+.TP
+.I fd_set
+.RS
+Include:
+.IR <sys/select.h> .
+Alternatively,
+.IR <sys/time.h> .
+.PP
+A structure type that can represent a set of file descriptors.
+According to POSIX,
+the maximum number of file descriptors in an
+.I fd_set
+structure is the value of the macro
+.BR FD_SETSIZE .
+.PP
+Conforming to:
+POSIX.1-2001 and later.
+.PP
+See also:
+.BR select (2)
+.RE
.\"------------------------------------- fenv_t -----------------------/
.TP
.I fenv_t
--
2.28.0
next prev parent reply other threads:[~2020-10-09 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 8:04 [PATCH] system_data_types.7: Add 'fd_set' Alejandro Colomar via Libc-alpha
2020-10-08 10:43 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-10-09 8:42 ` Alejandro Colomar via Libc-alpha [this message]
2020-10-10 9:06 ` Michael Kerrisk (man-pages) via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201009084243.8153-1-colomar.6.4.3@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=colomar.6.4.3@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).