Linux Manual Pages development
 help / color / mirror / Atom feed
From: ChaseKnowlden <haroldknowlden@gmail.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, ChaseKnowlden <haroldknowlden@gmail.com>
Subject: [PATCH] man/man2/seccomp.2: Fix signal.h type conflict with glibc in seccomp.2
Date: Wed, 20 May 2026 17:32:58 -0400	[thread overview]
Message-ID: <20260520213258.23500-1-haroldknowlden@gmail.com> (raw)

Signed-off-by: ChaseKnowlden <haroldknowlden@gmail.com>
---
 man/man2/seccomp.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/man2/seccomp.2 b/man/man2/seccomp.2
index e469f3997..8b8f2fc61 100644
--- a/man/man2/seccomp.2
+++ b/man/man2/seccomp.2
@@ -16,7 +16,7 @@ Standard C library
 .BR "#include <linux/seccomp.h>" "  /* Definition of " SECCOMP_* " constants */"
 .BR "#include <linux/filter.h>" "   /* Definition of " "struct sock_fprog" " */"
 .BR "#include <linux/audit.h>" "    /* Definition of " AUDIT_* " constants */"
-.BR "#include <linux/signal.h>" "   /* Definition of " SIG* " constants */"
+.BR "#include <signal.h>" "   /* Definition of " SIG* " constants */"
 .BR "#include <sys/ptrace.h>" "     /* Definition of " PTRACE_* " constants */"
 .\" Kees Cook noted: Anything that uses SECCOMP_RET_TRACE returns will
 .\"                  need <sys/ptrace.h>
-- 
2.54.0


             reply	other threads:[~2026-05-20 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 21:32 ChaseKnowlden [this message]
2026-05-20 23:10 ` [PATCH] man/man2/seccomp.2: Fix signal.h type conflict with glibc in seccomp.2 Alejandro Colomar

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=20260520213258.23500-1-haroldknowlden@gmail.com \
    --to=haroldknowlden@gmail.com \
    --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