All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Tycho Andersen <tycho@tycho.ws>
Subject: Re: [PATCH 2/2] Documentation: seccomp: unify list indentation
Date: Mon, 4 Mar 2019 12:49:32 -0800	[thread overview]
Message-ID: <CAGXu5jLaBQDAa5Jvudb1t53mUWu-Fywz6eD0Nf8weextAodFiQ@mail.gmail.com> (raw)
In-Reply-To: <20190304203152.8236-2-jwilk@jwilk.net>

On Mon, Mar 4, 2019 at 12:32 PM Jakub Wilk <jwilk@jwilk.net> wrote:
>
> Use tabs to indent SECCOMP_RET_USER_NOTIF definition, for consistency
> with other items in this list.
>
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>

Acked-by: Kees Cook <keescook@chromium.org>

-Kees

> ---
>  Documentation/userspace-api/seccomp_filter.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst
> index 0f09a63ea923..bd9165241b6c 100644
> --- a/Documentation/userspace-api/seccomp_filter.rst
> +++ b/Documentation/userspace-api/seccomp_filter.rst
> @@ -123,9 +123,9 @@ In precedence order, they are:
>         to userland as the errno without executing the system call.
>
>  ``SECCOMP_RET_USER_NOTIF``:
> -    Results in a ``struct seccomp_notif`` message sent on the userspace
> -    notification fd, if it is attached, or ``-ENOSYS`` if it is not. See below
> -    on discussion of how to handle user notifications.
> +       Results in a ``struct seccomp_notif`` message sent on the userspace
> +       notification fd, if it is attached, or ``-ENOSYS`` if it is not. See
> +       below on discussion of how to handle user notifications.
>
>  ``SECCOMP_RET_TRACE``:
>         When returned, this value will cause the kernel to attempt to
> --
> 2.20.1
>


-- 
Kees Cook

  reply	other threads:[~2019-03-04 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 20:31 [PATCH 1/2] Documentation: seccomp: fix reST markup Jakub Wilk
2019-03-04 20:31 ` [PATCH 2/2] Documentation: seccomp: unify list indentation Jakub Wilk
2019-03-04 20:49   ` Kees Cook [this message]
2019-03-18 18:00   ` Jonathan Corbet
2019-03-04 20:49 ` [PATCH 1/2] Documentation: seccomp: fix reST markup Kees Cook

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=CAGXu5jLaBQDAa5Jvudb1t53mUWu-Fywz6eD0Nf8weextAodFiQ@mail.gmail.com \
    --to=keescook@chromium.org \
    --cc=corbet@lwn.net \
    --cc=jwilk@jwilk.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=tycho@tycho.ws \
    /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.