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_run.2: SYNOPSIS: Fix prototype parameter types
Date: Mon, 15 Feb 2021 20:59:57 +0100 [thread overview]
Message-ID: <7fce9ade-3609-a03a-f486-511cbe2149a9@gmail.com> (raw)
In-Reply-To: <20210215131522.450666-7-alx.manpages@gmail.com>
Hi Alex,
On 2/15/21 2:15 PM, Alejandro Colomar wrote:
> The 2nd and 3rd parameters of spu_run() use 'uint32_t *'. Fix it.
>
> ......
>
> .../linux$ grep_syscall spu_run
> arch/powerpc/platforms/cell/spu_syscalls.c:80:
> SYSCALL_DEFINE3(spu_run,int, fd, __u32 __user *, unpc, __u32 __user *, ustatus)
> include/linux/syscalls.h:1034:
> asmlinkage long sys_spu_run(int fd, __u32 __user *unpc,
> __u32 __user *ustatus);
> .../linux$
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks! Patch applied.
Cheers,
Michael
> ---
> man2/spu_run.2 | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/man2/spu_run.2 b/man2/spu_run.2
> index fb1879759..8b2a64ebb 100644
> --- a/man2/spu_run.2
> +++ b/man2/spu_run.2
> @@ -30,8 +30,7 @@ spu_run \- execute an SPU context
> .nf
> .B #include <sys/spu.h>
> .PP
> -.BI "int spu_run(int " fd ", unsigned int *" npc \
> -", unsigned int *" event ");"
> +.BI "int spu_run(int " fd ", uint32_t *" npc ", uint32_t *" event );
> .fi
> .PP
> .IR Note :
>
--
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_run.2: SYNOPSIS: Fix prototype parameter types 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=7fce9ade-3609-a03a-f486-511cbe2149a9@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