Linux Manual Pages development
 help / color / mirror / Atom feed
From: funsafemath <funsafemath@proton.me>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH] man/man2/seccomp_unotify.2: wfix
Date: Mon, 18 May 2026 05:20:27 +0100	[thread overview]
Message-ID: <agqTcfOqY8Jq06Ff@nix-mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

There are two documented flags, but the sentence states there is only one.

Signed-off-by: funsafemath <funsafemath@proton.me>
---
 man/man2/seccomp_unotify.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man/man2/seccomp_unotify.2 b/man/man2/seccomp_unotify.2
index a5c1a4423..0b4fc7239 100644
--- a/man/man2/seccomp_unotify.2
+++ b/man/man2/seccomp_unotify.2
@@ -716,22 +716,22 @@ .SS SECCOMP_IOCTL_NOTIF_ADDFD
 .in
 .P
 The fields in this structure are as follows:
 .TP
 .I id
 This field should be set to the notification ID
 (cookie value) that was obtained via
 .BR SECCOMP_IOCTL_NOTIF_RECV .
 .TP
 .I flags
-This field is a bit mask of flags that modify the behavior of the operation.
-Currently, only one flag is supported:
+This field is a bit mask of flags that modify the behavior of the operation,
+as described below:
 .RS
 .TP
 .B SECCOMP_ADDFD_FLAG_SETFD
 When allocating the file descriptor in the target,
 use the file descriptor number specified in the
 .I newfd
 field.
 .TP
 .BR SECCOMP_ADDFD_FLAG_SEND " (since Linux 5.14)"
 .\" commit 0ae71c7720e3ae3aabd2e8a072d27f7bd173d25c
-- 
2.52.0


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

                 reply	other threads:[~2026-05-18  4:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=agqTcfOqY8Jq06Ff@nix-mail \
    --to=funsafemath@proton.me \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.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