public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrei Vagin <avagin@google.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, Tycho Andersen <tycho@tycho.ws>,
	Andrei Vagin <avagin@google.com>,
	kernel test robot <lkp@intel.com>
Subject: [PATCH] seccomp: fix the kernel-doc comment for the notification structure
Date: Thu, 17 Aug 2023 16:26:18 -0700	[thread overview]
Message-ID: <20230817232618.3022269-1-avagin@google.com> (raw)

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>
---
 kernel/seccomp.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/kernel/seccomp.c b/kernel/seccomp.c
index d3fdc0086168..732fca979e8b 100644
--- a/kernel/seccomp.c
+++ b/kernel/seccomp.c
@@ -141,11 +141,10 @@ struct seccomp_kaddfd {
  * @request: A semaphore that users of this notification can wait on for
  *           changes. Actual reads and writes are still controlled with
  *           filter->notify_lock.
+ * @flags: A set of SECCOMP_USER_NOTIF_FD_* flags.
  * @next_id: The id of the next request.
  * @notifications: A list of struct seccomp_knotif elements.
- * @flags: A set of SECCOMP_USER_NOTIF_FD_* flags.
  */
-
 struct notification {
 	atomic_t requests;
 	u32 flags;
-- 
2.42.0.rc1.204.g551eb34607-goog


             reply	other threads:[~2023-08-17 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 23:26 Andrei Vagin [this message]
2023-08-17 23:48 ` [PATCH] seccomp: fix the kernel-doc comment for the notification structure 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=20230817232618.3022269-1-avagin@google.com \
    --to=avagin@google.com \
    --cc=keescook@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox