On Mon, Mar 4, 2019 at 12:32 PM Jakub Wilk <jw...@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 <jw...@jwilk.net>

Acked-by: Kees Cook <keesc...@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 via email to