From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@google.com>
Cc: linux-kernel@vger.kernel.org, Tycho Andersen <tycho@tycho.ws>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] seccomp: fix the kernel-doc comment for the notification structure
Date: Thu, 17 Aug 2023 16:48:54 -0700 [thread overview]
Message-ID: <202308171648.4D19FBA@keescook> (raw)
In-Reply-To: <20230817232618.3022269-1-avagin@google.com>
On Thu, Aug 17, 2023 at 04:26:18PM -0700, Andrei Vagin wrote:
> Remove an empty line and resort parameters in the comment.
>
> Fixes: 48a1084a8b74 ("seccomp: add the synchronous mode for seccomp_unotify")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202308171742.AncabIG1-lkp@intel.com/
> Signed-off-by: Andrei Vagin <avagin@google.com>
Thanks! I actually just sent this patch earlier, which fixes all of the
warnings being reported for the kerndoc build:
https://lore.kernel.org/lkml/20230817194302.never.378-kees@kernel.org/
--
Kees Cook
prev parent reply other threads:[~2023-08-17 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 23:26 [PATCH] seccomp: fix the kernel-doc comment for the notification structure Andrei Vagin
2023-08-17 23:48 ` Kees Cook [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=202308171648.4D19FBA@keescook \
--to=keescook@chromium.org \
--cc=avagin@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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.