All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:06:16 +0100	[thread overview]
Message-ID: <20240212120616.GH21691@gnu.wildebeest.org> (raw)
In-Reply-To: <Zcl5HJ7XS6gPvhzg@debian>

Hi Alejandro,

On Mon, Feb 12, 2024 at 02:49:16AM +0100, Alejandro Colomar wrote:
> 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 */
> 

Aha, ok, the other comment. Will reword for V3.

> 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).

Yeah, max 79 max sense (all my terminals are 80 chars wide).
Formatting the comment is a little tricky, but I believe I got it.

Cheers,

Mark


      reply	other threads:[~2024-02-12 12:06 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
2024-02-12 12:06       ` Mark Wielaard [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=20240212120616.GH21691@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 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.