From: Alejandro Colomar <alx@kernel.org>
To: Mark Wielaard <mark@klomp.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 02:49:16 +0100 [thread overview]
Message-ID: <Zcl5HJ7XS6gPvhzg@debian> (raw)
In-Reply-To: <20240212000531.GG21691@gnu.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Hi Mark,
On Mon, Feb 12, 2024 at 01:05:31AM +0100, Mark Wielaard wrote:
> > > .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.
Sure; no problem!
When we include a header not for a function but for constants, we
specify which are those constants. For example, membarrier(2) has
#include <linux/membarrier.h> /* Definition of MEMBARRIER_* constants */
#include <sys/syscall.h> /* Definition of SYS_* constants */
Here, I'd use
#include <linux/close_range.h> /* Definition of CLOSE_RANGE_* constants */
BTW, I notice that it's near the 80-column limit. We try to limit
ourselves to 79 columns, for an obscure reason. For that, we'll need to
use only 1 space before the comment (otherwise, I'd agree to use 2).
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-12 1:49 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
2024-02-12 1:49 ` Alejandro Colomar [this message]
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=Zcl5HJ7XS6gPvhzg@debian \
--to=alx@kernel.org \
--cc=ahajkova@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mark@klomp.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.