All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Stephen Kitt <steve@sk2.org>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 1/5] mq_notify.3: Add signal.h for SIGEV_ constants
Date: Sat, 8 Jan 2022 20:42:40 +0100	[thread overview]
Message-ID: <9c56ea6e-11b8-5fe3-64a2-97b3e76dcb9c@gmail.com> (raw)
In-Reply-To: <20220108154304.1030478-1-steve@sk2.org>

On 1/8/22 16:43, Stephen Kitt 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.
> 
> Signed-off-by: Stephen Kitt <steve@sk2.org>

Patch applied, Stephen.

Thanks,

Alex

> ---
>   man3/mq_notify.3 | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/man3/mq_notify.3 b/man3/mq_notify.3
> index 2c35a347d..222108d61 100644
> --- a/man3/mq_notify.3
> +++ b/man3/mq_notify.3
> @@ -28,6 +28,7 @@ mq_notify \- register for notification when a message is available
>   .SH SYNOPSIS
>   .nf
>   .B #include <mqueue.h>
> +.BR "#include <signal.h>           " "/* Definition of SIGEV_* constants */"
>   .PP
>   .BI "int mq_notify(mqd_t " mqdes ", const struct sigevent *" sevp );
>   .fi
> @@ -224,6 +225,7 @@ queue and then terminates the process.
>   #include <stdio.h>
>   #include <stdlib.h>
>   #include <unistd.h>
> +#include <signal.h>
>   
>   #define handle_error(msg) \e
>       do { perror(msg); exit(EXIT_FAILURE); } while (0)
> 
> base-commit: 88d2b3fdef39603bc6a608a0d814d1800b6a4089

-- 
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      parent reply	other threads:[~2022-01-08 19:42 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 ` [PATCH 1/5] mq_notify.3: Add signal.h for SIGEV_ constants Stephen Kitt
2022-01-08 19:42 ` Alejandro Colomar (man-pages) [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=9c56ea6e-11b8-5fe3-64a2-97b3e76dcb9c@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=steve@sk2.org \
    /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.