All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] execveat.2: Remove unused include
Date: Tue, 11 May 2021 05:17:39 +1200	[thread overview]
Message-ID: <a1e2e2a8-c998-bcbd-62c7-c1ee8f75ae17@gmail.com> (raw)
In-Reply-To: <20210510130209.4578-1-alx.manpages@gmail.com>

Hi Alex,

On 5/11/21 1:02 AM, Alejandro Colomar wrote:
> This complements commit e3eba861bd966911b38b7ebc572f0c092ca7bdee.
> 
> Since we don't need syscall(2) anymore, we don't need SYS_* definitions.
> 
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
>  man2/execveat.2 | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/man2/execveat.2 b/man2/execveat.2
> index 11ae04a9f..495617b09 100644
> --- a/man2/execveat.2
> +++ b/man2/execveat.2
> @@ -29,7 +29,6 @@ execveat \- execute program relative to a directory file descriptor
>  .SH SYNOPSIS
>  .nf
>  .BR "#include <linux/fcntl.h>" "      /* Definition of " AT_* " constants */"
> -.BR "#include <sys/syscall.h>" "      /* Definition of " SYS_* " constants */"
>  .B #include <unistd.h>
>  .PP
>  .BI "int execveat(int " dirfd ", const char *" pathname ,


Thanks. Patch applied.

I've now pushed everything from you that I have applied.
("[PATCH] Makefile: Simplify error handling" remains open.)

Cheers,

Michael


-- 
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:[~2021-05-10 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 13:02 [PATCH] execveat.2: Remove unused include Alejandro Colomar
2021-05-10 17:17 ` 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=a1e2e2a8-c998-bcbd-62c7-c1ee8f75ae17@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --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.