From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Alejandro Colomar <colomar.6.4.3@gmail.com>
Subject: [PATCH 3/9] system_data_types.7: Document sigevent
Date: Fri, 18 Sep 2020 19:04:37 +0200 [thread overview]
Message-ID: <20200918170442.94920-4-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20200918170442.94920-1-colomar.6.4.3@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man7/system_data_types.7 | 57 ++++++++++++++++++++++++++++++++++++----
1 file changed, 52 insertions(+), 5 deletions(-)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index 48871e4eb..53c289e31 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -133,6 +133,51 @@ and
.I ssize_t
types in this page.
.TP
+.I sigevent
+.IP
+Include:
+.IR <signal.h> ;
+or
+.I <aio.h>
+or
+.I <mqueue.h>
+or
+.IR <time.h> .
+.IP
+.EX
+struct sigevent {
+ int sigev_notify; /* Notification type */
+ int sigev_signo; /* Signal number */
+ union sigval sigev_value; /* Signal value */
+ void (*sigev_notify_function)(union sigval);
+ /* Notification function */
+ pthread_attr_t *sigev_notify_attributes;
+ /* Notification attributes */
+};
+.EE
+.\".IP
+.\" FIXME: Add a description?
+.IP
+Conforming to: POSIX.1-2001 and later.
+.IP
+Notes:
+.I <aio.h>
+and
+.I <time.h>
+define
+.I sigevent
+since POSIX.1-2008.
+.IP
+See also:
+.BR timer_create (2),
+.BR getaddrinfo_a (3),
+.BR lio_listio (3),
+.BR mq_notify (3)
+.\".IP
+.\"See also the
+.\".I aiocb FIXME
+.\"structure in this page.
+.TP
.I sigval
.IP
Include:
@@ -153,12 +198,14 @@ See also:
.BR pthread_sigqueue (3),
.BR sigqueue (3),
.BR sigevent (7)
-.\".IP
-.\"See also the
-.\".I sigevent FIXME
-.\"structure and the
+.IP
+See also the
+.I sigevent
+structure
+.\"and the
.\".I siginfo_t FIXME
-.\"type in this page.
+.\"type
+in this page.
.TP
.I size_t
.IP
--
2.28.0
next prev parent reply other threads:[~2020-09-18 17:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 17:04 [PATCH 0/9] Document aiocb, sigevent, siginfo_t Alejandro Colomar
2020-09-18 17:04 ` [PATCH 1/9] system_data_types.7: ffix Alejandro Colomar
2020-09-18 20:49 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 2/9] system_data_types.7: srcfix: Add FIXME note: Add descriptions Alejandro Colomar
2020-09-18 20:50 ` Michael Kerrisk (man-pages)
2020-09-18 21:03 ` Michael Kerrisk (man-pages)
2020-09-18 21:35 ` Alejandro Colomar
2020-09-18 17:04 ` Alejandro Colomar [this message]
2020-09-18 21:09 ` [PATCH 3/9] system_data_types.7: Document sigevent Michael Kerrisk (man-pages)
2020-09-18 21:36 ` Alejandro Colomar
2020-09-18 17:04 ` [PATCH 4/9] sigevent.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 21:10 ` Michael Kerrisk (man-pages)
2020-09-18 21:39 ` Alejandro Colomar
2020-09-18 21:43 ` Michael Kerrisk (man-pages)
2020-09-18 21:57 ` Alejandro Colomar
2020-09-19 8:11 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 5/9] system_data_types.7: srcfix: cosmetic: Visually sparate types Alejandro Colomar
2020-09-18 21:14 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 6/9] system_data_types.7: Document aiocb Alejandro Colomar
2020-09-18 17:04 ` [PATCH 7/9] aiocb.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 21:28 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 8/9] system_data_types.7: Document siginfo_t Alejandro Colomar
2020-09-18 21:42 ` Michael Kerrisk (man-pages)
2020-09-18 21:45 ` Alejandro Colomar
2020-09-20 18:05 ` [PATCH v2 " Alejandro Colomar
2020-09-20 20:19 ` Michael Kerrisk (man-pages)
2020-09-20 18:05 ` [PATCH v2 9/9] siginfo_t.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-20 20:19 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH " Alejandro Colomar
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=20200918170442.94920-4-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--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