From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org,
Eugene Syromyatnikov <evgsyr@gmail.com>
Subject: [PATCH] keyctl.2: SYNOPSIS: Fix prototype parameter types
Date: Wed, 30 Dec 2020 22:41:44 +0100 [thread overview]
Message-ID: <20201230214147.874671-4-alx.manpages@gmail.com> (raw)
The Linux kernel uses 'unsigned long'.
There's no reason to use the typedef '__kernel_ulong_t'.
......
$ syscall='keyctl';
$ find linux/ -type f -name '*.c' \
|xargs pcregrep -Mn "(?s)^[\w_]*SYSCALL_DEFINE.\(${syscall},.*?\)";
linux/security/keys/keyctl.c:1869:
SYSCALL_DEFINE5(keyctl, int, option, unsigned long, arg2, unsigned long, arg3,
unsigned long, arg4, unsigned long, arg5)
linux/security/keys/compat.c:17:
COMPAT_SYSCALL_DEFINE5(keyctl, u32, option,
u32, arg2, u32, arg3, u32, arg4, u32, arg5)
Cc: Eugene Syromyatnikov <evgsyr@gmail.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man2/keyctl.2 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 9311100cf..ea3a5d3dd 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -40,9 +40,9 @@ keyctl \- manipulate the kernel's key management facility
.B #include <linux/keyctl.h>
.B #include <unistd.h>
.PP
-.BI "long syscall(__NR_keyctl, int " operation ", __kernel_ulong_t " arg2 ,
-.BI " __kernel_ulong_t " arg3 ", __kernel_ulong_t " arg4 ,
-.BI " __kernel_ulong_t " arg5 );
+.BI "long syscall(__NR_keyctl, int " operation ", unsigned long " arg2 ,
+.BI " unsigned long " arg3 ", unsigned long " arg4 ,
+.BI " unsigned long " arg5 );
.fi
.PP
.IR Note :
--
2.29.2
next reply other threads:[~2020-12-30 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 21:41 Alejandro Colomar [this message]
2020-12-30 22:37 ` [PATCH] keyctl.2: SYNOPSIS: Fix prototype parameter types Michael Kerrisk (man-pages)
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=20201230214147.874671-4-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=evgsyr@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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