linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Petr Vorel <pvorel@suse.cz>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, Li Wang <liwang@redhat.com>,
	Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [PATCH 1/1] syscall.2: Update Feature Test Macro Requirements
Date: Fri, 10 Jan 2020 21:13:13 +0100	[thread overview]
Message-ID: <aa304ca3-1ba3-faf8-c8cb-2abea26eca63@gmail.com> (raw)
In-Reply-To: <20200109154626.6206-1-pvorel@suse.cz>

Hello Petr,

On 1/9/20 4:46 PM, Petr Vorel wrote:
> Reported-by: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>

Thanks. Patch applied.

Cheers,

Michael

> ---
>  man2/syscall.2 | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index 9091b34bb..3fc32cb7a 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -44,12 +44,22 @@
>  syscall \- indirect system call
>  .SH SYNOPSIS
>  .nf
> -.BR "#define _GNU_SOURCE" "         /* See feature_test_macros(7) */"
>  .B #include <unistd.h>
>  .BR "#include <sys/syscall.h>   "  "/* For SYS_xxx definitions */"
>  .PP
>  .BI "long syscall(long " number ", ...);"
>  .fi
> +.PP
> +.in -4n
> +Feature Test Macro Requirements for glibc (see
> +.BR feature_test_macros (7)):
> +.in
> +.PP
> +.BR syscall ():
> +.ad l
> +    /* Since glibc 2.19: */ _DEFAULT_SOURCE
> +    /* Glibc versions <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE
> +.ad
>  .SH DESCRIPTION
>  .BR syscall ()
>  is a small library function that invokes
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2020-01-10 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 15:46 [PATCH 1/1] syscall.2: Update Feature Test Macro Requirements Petr Vorel
2020-01-10 20:13 ` Michael Kerrisk (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=aa304ca3-1ba3-faf8-c8cb-2abea26eca63@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=chrubis@suse.cz \
    --cc=linux-man@vger.kernel.org \
    --cc=liwang@redhat.com \
    --cc=pvorel@suse.cz \
    /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).