From: Stephen Kitt <steve@sk2.org>
To: Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/5] mq_notify.3: Add signal.h for SIGEV_ constants
Date: Sat, 8 Jan 2022 17:02:10 +0100 [thread overview]
Message-ID: <20220108170210.7c637f0c@heffalump.sk2.org> (raw)
In-Reply-To: <20220108154304.1030478-1-steve@sk2.org>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On Sat, 8 Jan 2022 16:43:00 +0100, Stephen Kitt <steve@sk2.org> wrote:
> The example program needs signal.h to build correctly, since the
> SIGEV_ constants are defined through signal.h; also document that in
> the synopsis.
Sorry, I forgot the v2 marker for all of these...
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-08 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 15:43 [PATCH 1/5] mq_notify.3: Add signal.h for SIGEV_ constants Stephen Kitt
2022-01-08 15:43 ` [PATCH 2/5] newlocale.3: Use LC_GLOBAL_LOCALE, not ..._HANDLE Stephen Kitt
2022-01-08 19:44 ` Alejandro Colomar (man-pages)
2022-01-08 15:43 ` [PATCH 3/5] pkeys.7: Update the example to match glibc Stephen Kitt
2022-01-08 19:49 ` Alejandro Colomar (man-pages)
2022-01-08 15:43 ` [PATCH 4/5] pkeys.7: Rely on the glibc implementations Stephen Kitt
2022-01-08 15:43 ` [PATCH 5/5] strtok.3: Fix j/str1 declaration Stephen Kitt
2022-01-08 19:51 ` Alejandro Colomar (man-pages)
2022-01-08 16:02 ` Stephen Kitt [this message]
2022-01-08 19:42 ` [PATCH 1/5] mq_notify.3: Add signal.h for SIGEV_ constants Alejandro Colomar (man-pages)
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=20220108170210.7c637f0c@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=alx.manpages@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.