From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
To: "Dmitry V. Levin" <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] sigprocmask.2: do not specify an exact value of rt_sigprocmask's 4th argument
Date: Mon, 20 Feb 2017 09:17:07 +0100 [thread overview]
Message-ID: <58AAA603.6020400@bfs.de> (raw)
In-Reply-To: <20170219211302.GA30235-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Am 19.02.2017 22:13, schrieb Dmitry V. Levin:
> As sizeof(kernel_sigset_t) is not the same for all architectures,
> it would be better not to mention any numbers as its value.
>
> Signed-off-by: Dmitry V. Levin <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
> ---
> man2/sigprocmask.2 | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/man2/sigprocmask.2 b/man2/sigprocmask.2
> index 8388340..6379a4d 100644
> --- a/man2/sigprocmask.2
> +++ b/man2/sigprocmask.2
> @@ -202,10 +202,11 @@ which specifies the size in bytes of the signal sets in
> .IR set
> and
> .IR oldset .
> -This argument is currently required to have the value 8
> -(
> -.IR sizeof(kernel_sigset_t)
> -).
> +This argument is currently required to have a fixed value
> +(equal to
> +.IR sizeof(kernel_sigset_t) ).
> +.\" sizeof(kernel_sigset_t) == _NSIG / 8,
> +.\" which equals to 8 on most architectures, but e.g. on MIPS it's 16.
>
> The glibc
> .BR sigprocmask ()
why not add this information like:
Note: sizeof(kernel_sigset_t) is not the same for all architectures
re,
wh
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-20 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 21:13 [PATCH] sigprocmask.2: do not specify an exact value of rt_sigprocmask's 4th argument Dmitry V. Levin
[not found] ` <20170219211302.GA30235-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
2017-02-20 8:17 ` walter harms [this message]
[not found] ` <58AAA603.6020400-fPG8STNUNVg@public.gmane.org>
2017-02-20 15:43 ` [PATCH v2] " Dmitry V. Levin
[not found] ` <20170220154327.GA9511-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
2017-03-15 9:49 ` [PING] " Dmitry V. Levin
2017-03-24 14:40 ` Michael Kerrisk (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=58AAA603.6020400@bfs.de \
--to=wharms-fpg8stnunvg@public.gmane.org \
--cc=ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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 NNTP newsgroup(s).