linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Tyler Hicks <tyhicks@canonical.com>,
	Will Drewry <wad@chromium.org>
Subject: Re: [PATCH v2 03/10] seccomp.2: Document why each header is needed
Date: Mon, 24 May 2021 21:34:17 +0200	[thread overview]
Message-ID: <cd876e7c-7236-8530-e0a7-b2940587ad42@gmail.com> (raw)
In-Reply-To: <20210524181947.459437-3-alx.manpages@gmail.com>

Hi Michael,

On 5/24/21 8:19 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Tyler Hicks <tyhicks@canonical.com>
> Cc: Will Drewry <wad@chromium.org>
> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
> ---

Please discards this one, for the same reasons as in v1: repeated.
See 
<https://lore.kernel.org/linux-man/20210515182254.186607-1-alx.manpages@gmail.com/T/#u> 
instead.

That one has a better mail.

Thanks,

Alex


>   man2/seccomp.2 | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/man2/seccomp.2 b/man2/seccomp.2
> index 584a16f22..1be7d6766 100644
> --- a/man2/seccomp.2
> +++ b/man2/seccomp.2
> @@ -30,11 +30,11 @@
>   seccomp \- operate on Secure Computing state of the process
>   .SH SYNOPSIS
>   .nf
> -.B #include <linux/seccomp.h>
> -.B #include <linux/filter.h>
> -.B #include <linux/audit.h>
> -.B #include <linux/signal.h>
> -.B #include <sys/ptrace.h>
> +.BR "#include <linux/seccomp.h>" "  /* Definition of " SECCOMP_* " constants */"
> +.BR "#include <linux/filter.h>" "   /* Definition of " "struct sock_fprog" " */"
> +.BR "#include <linux/audit.h>" "    /* Definition of " AUDIT_* " constants */"
> +.BR "#include <linux/signal.h>" "   /* Definition of " SIG* " constants */"
> +.BR "#include <sys/ptrace.h>" "     /* Definition of " PTRACE_* " constants */"
>   .\" Kees Cook noted: Anything that uses SECCOMP_RET_TRACE returns will
>   .\"                  need <sys/ptrace.h>
>   .PP
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-05-24 19:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 23:25 [PATCH 00/10] man2: SYNOPSIS: Use syscall, and fix includes Alejandro Colomar
2021-05-21 23:25 ` [PATCH 01/10] open.2: Remove unused <sys/stat.h> Alejandro Colomar
2021-05-21 23:25 ` [PATCH 02/10] rt_sigqueueinfo.2: Use syscall(SYS_...); for system calls without a wrapper Alejandro Colomar
2021-05-21 23:25 ` [PATCH 04/10] seccomp.2: " Alejandro Colomar
2021-05-21 23:25 ` [PATCH 05/10] set_thread_area.2: " Alejandro Colomar
2021-05-21 23:25 ` [PATCH 06/10] set_tid_address.2: " Alejandro Colomar
2021-05-21 23:25 ` [PATCH 07/10] sgetmask.2: " Alejandro Colomar
2021-05-21 23:25 ` [PATCH 08/10] shmop.2: Remove unused include Alejandro Colomar
2021-05-21 23:25 ` [PATCH 09/10] sigprocmask.2: Use syscall(SYS_...); for raw system calls Alejandro Colomar
2021-05-21 23:25 ` [PATCH 10/10] socketcall.2: Use syscall(SYS_...); for system calls without a wrapper Alejandro Colomar
2021-05-24 18:19   ` [PATCH v2 01/10] open.2: Remove unused <sys/stat.h> Alejandro Colomar
2021-06-09 22:23     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 02/10] rt_sigqueueinfo.2: Use syscall(SYS_...); for system calls without a wrapper Alejandro Colomar
2021-06-09 22:24     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 03/10] seccomp.2: Document why each header is needed Alejandro Colomar
2021-05-24 19:34     ` Alejandro Colomar (man-pages) [this message]
2021-06-09 22:30       ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 04/10] seccomp.2: Use syscall(SYS_...); for system calls without a wrapper Alejandro Colomar
2021-06-09 22:31     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 05/10] set_thread_area.2: " Alejandro Colomar
2021-06-09 22:24     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 06/10] set_tid_address.2: " Alejandro Colomar
2021-06-09 22:25     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 07/10] sgetmask.2: " Alejandro Colomar
2021-06-09 22:25     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 08/10] shmop.2: Remove unused include Alejandro Colomar
2021-06-09 22:25     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 09/10] sigprocmask.2: Use syscall(SYS_...); for raw system calls Alejandro Colomar
2021-06-09 22:26     ` Michael Kerrisk (man-pages)
2021-05-24 18:19   ` [PATCH v2 10/10] socketcall.2: Use syscall(SYS_...); for system calls without a wrapper Alejandro Colomar
2021-06-09 22:27     ` Michael Kerrisk (man-pages)
2021-05-24 19:09 ` [PATCH 00/10] man2: SYNOPSIS: Use syscall, and fix includes Alejandro Colomar (man-pages)
2021-06-09 22:28   ` Michael Kerrisk (man-pages)
2021-06-09 22:29   ` Michael Kerrisk (man-pages)

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=cd876e7c-7236-8530-e0a7-b2940587ad42@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tyhicks@canonical.com \
    --cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).