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] pciconfig_read.2: SYNOPSIS: Fix prototype parameter types
Date: Mon, 15 Feb 2021 21:12:44 +0100 [thread overview]
Message-ID: <f8b208a9-b698-d0d3-f4d0-45f042b9fdc5@gmail.com> (raw)
In-Reply-To: <20210215131522.450666-12-alx.manpages@gmail.com>
Hi Alex,
On 2/15/21 2:15 PM, Alejandro Colomar wrote:
> Use the glibc prototypes instead of the kernel ones.
> Exception: use 'int' instead of 'enum'.
>
> ......
>
> .../glibc$ grep_glibc_prototype pciconfig_read
> sysdeps/unix/sysv/linux/alpha/sys/io.h:72:
> extern int pciconfig_read (unsigned long int __bus,
> unsigned long int __dfn,
> unsigned long int __off,
> unsigned long int __len,
> unsigned char *__buf) __THROW;
> sysdeps/unix/sysv/linux/ia64/sys/io.h:57:
> extern int pciconfig_read (unsigned long int __bus, unsigned long int __dfn,
> unsigned long int __off, unsigned long int __len,
> unsigned char *__buf);
> .../glibc$ grep_glibc_prototype pciconfig_write
> sysdeps/unix/sysv/linux/alpha/sys/io.h:78:
> extern int pciconfig_write (unsigned long int __bus,
> unsigned long int __dfn,
> unsigned long int __off,
> unsigned long int __len,
> unsigned char *__buf) __THROW;
> sysdeps/unix/sysv/linux/ia64/sys/io.h:61:
> extern int pciconfig_write (unsigned long int __bus, unsigned long int __dfn,
> unsigned long int __off, unsigned long int __len,
> unsigned char *__buf);
> .../glibc$ grep_glibc_prototype pciconfig_iobase
> sysdeps/unix/sysv/linux/alpha/sys/io.h:66:
> extern long pciconfig_iobase(enum __pciconfig_iobase_which __which,
> unsigned long int __bus,
> unsigned long int __dfn)
> __THROW __attribute__ ((const));
> .../glibc$
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks! Patch applied.
Cheers,
Michael
> ---
> man2/pciconfig_read.2 | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/man2/pciconfig_read.2 b/man2/pciconfig_read.2
> index cec6f58e9..c379e2d3b 100644
> --- a/man2/pciconfig_read.2
> +++ b/man2/pciconfig_read.2
> @@ -13,11 +13,13 @@ pciconfig_read, pciconfig_write, pciconfig_iobase \- pci device information hand
> .B #include <pci.h>
> .PP
> .BI "int pciconfig_read(unsigned long " bus ", unsigned long " dfn ,
> -.BI " unsigned long " off ", unsigned long " len ", void *" buf );
> +.BI " unsigned long " off ", unsigned long " len ,
> +.BI " unsigned char *" buf );
> .BI "int pciconfig_write(unsigned long " bus ", unsigned long " dfn ,
> -.BI " unsigned long " off ", unsigned long " len ", void *" buf );
> -.BI "int pciconfig_iobase(long " which ", unsigned long " bus ,
> -.BI " unsigned long " devfn );
> +.BI " unsigned long " off ", unsigned long " len ,
> +.BI " unsgined char *" buf );
> +.BI "int pciconfig_iobase(int " which ", unsigned long " bus ,
> +.BI " unsigned long " devfn );
> .fi
> .SH DESCRIPTION
> Most of the interaction with PCI devices is already handled by the
>
--
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:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:15 [PATCH] pciconfig_read.2: SYNOPSIS: Fix prototype parameter types Alejandro Colomar
2021-02-15 20:12 ` 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=f8b208a9-b698-d0d3-f4d0-45f042b9fdc5@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