From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] spu_create.2: SYNOPSIS: Fix prototype parameter type
Date: Mon, 15 Feb 2021 20:59:39 +0100 [thread overview]
Message-ID: <e748f71b-ba30-ccff-2e1c-44fb1d4d2c7f@gmail.com> (raw)
In-Reply-To: <20210215131522.450666-6-alx.manpages@gmail.com>
Hi Alex,
On 2/15/21 2:15 PM, Alejandro Colomar wrote:
> The 'flags' parameter of spu_create() uses 'unsigned int'. Fix it.
>
> ......
>
> .../linux$ grep_syscall spu_create
> arch/powerpc/platforms/cell/spu_syscalls.c:56:
> SYSCALL_DEFINE4(spu_create, const char __user *, name, unsigned int, flags,
> umode_t, mode, int, neighbor_fd)
> include/linux/syscalls.h:1036:
> asmlinkage long sys_spu_create(const char __user *name,
> unsigned int flags, umode_t mode, int fd);
> .../linux$
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks! Patch applied.
Cheers,
Michael
> ---
> man2/spu_create.2 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man2/spu_create.2 b/man2/spu_create.2
> index ff0dbdc20..2493b16bc 100644
> --- a/man2/spu_create.2
> +++ b/man2/spu_create.2
> @@ -30,7 +30,8 @@ spu_create \- create a new spu context
> .B #include <sys/types.h>
> .B #include <sys/spu.h>
> .PP
> -.BI "int spu_create(const char *" pathname ", int " flags ", mode_t " mode ","
> +.BI "int spu_create(const char *" pathname ", unsigned int " flags \
> +", mode_t " mode ,
> .BI " int " neighbor_fd ");"
> .fi
> .PP
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-02-15 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:15 [PATCH] spu_create.2: SYNOPSIS: Fix prototype parameter type Alejandro Colomar
2021-02-15 19:59 ` Michael Kerrisk (man-pages) [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=e748f71b-ba30-ccff-2e1c-44fb1d4d2c7f@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--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