From: Mark Wielaard <mark@klomp.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, "Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: [PATCH v2] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS
Date: Mon, 12 Feb 2024 01:05:31 +0100 [thread overview]
Message-ID: <20240212000531.GG21691@gnu.wildebeest.org> (raw)
In-Reply-To: <ZcldDOM_i6u742Pf@debian>
Hi Alejandro,
On Mon, Feb 12, 2024 at 12:49:32AM +0100, Alejandro Colomar wrote:
> Thanks! LGTM, but please check a small comment below.
>
> > ---
> > man2/close_range.2 | 10 ++++++----
> > 1 file changed, 6 insertions(+), 4 deletions(-)
> >
> > diff --git a/man2/close_range.2 b/man2/close_range.2
> > index 380a47365..62b728e96 100644
> > --- a/man2/close_range.2
> > +++ b/man2/close_range.2
> > @@ -11,10 +11,13 @@ Standard C library
> > .RI ( libc ", " \-lc )
> > .SH SYNOPSIS
> > .nf
> > -.B #include <linux/close_range.h>
> > +.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
> > +.B #include <unistd.h>
> > +.P
> > +.BR "#include <linux/close_range.h>" " /* For the flags constants */"
>
> Could you please format the comment like other pages that do the same
> thing? See for example membarrier(2).
Sorry, you have to be more explicit what exactly you believe is not
the same thing that other pages do. membarrier.2 doesn't need a
_GNU_SOURCE define and I believe I used the comment as other pages
that do.
Cheers,
Mark
next prev parent reply other threads:[~2024-02-12 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 23:29 [PATCH v2] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Mark Wielaard
2024-02-11 23:49 ` Alejandro Colomar
2024-02-12 0:05 ` Mark Wielaard [this message]
2024-02-12 1:49 ` Alejandro Colomar
2024-02-12 12:06 ` Mark Wielaard
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=20240212000531.GG21691@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=ahajkova@redhat.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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