From: Randy Dunlap <rdunlap@infradead.org>
To: Wang Wenhu <wenhu.wang@vivo.com>,
arnd@arndb.de, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kernel@vivo.com
Subject: Re: [PATCH] io: correct documentation mismatches for io memcpy
Date: Wed, 22 Apr 2020 09:42:56 -0700 [thread overview]
Message-ID: <4b0a80ed-a639-c8c0-e6c3-01ba3266b7de@infradead.org> (raw)
In-Reply-To: <20200422092905.39529-1-wenhu.wang@vivo.com>
Hi--
2 small nits: please see below.
On 4/22/20 2:29 AM, Wang Wenhu wrote:
> Minor mismatches exist between funtion documentations and parameter
> definitions.
>
> Function definition lines are as following:
> static inline void memcpy_fromio(void *buffer,
> const volatile void __iomem *addr,
> size_t size)
>
> static inline void memcpy_toio(volatile void __iomem *addr, const void *buffer,
> size_t size)
>
> Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>
> ---
> include/asm-generic/io.h | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/include/asm-generic/io.h b/include/asm-generic/io.h
> index d39ac997dda8..63131ec4857f 100644
> --- a/include/asm-generic/io.h
> +++ b/include/asm-generic/io.h
> @@ -1067,9 +1067,9 @@ static inline void memset_io(volatile void __iomem *addr, int value,
> #define memcpy_fromio memcpy_fromio
> /**
> * memcpy_fromio Copy a block of data from I/O memory
This needs a dash ('-') between the function name & its description.
> - * @dst: The (RAM) destination for the copy
> - * @src: The (I/O memory) source for the data
> - * @count: The number of bytes to copy
> + * @buffer: The (RAM) destination for the copy
> + * @addr: The (I/O memory) source for the data
> + * @size: The number of bytes to copy
> *
> * Copy a block of data from I/O memory.
> */
> @@ -1085,9 +1085,9 @@ static inline void memcpy_fromio(void *buffer,
> #define memcpy_toio memcpy_toio
> /**
> * memcpy_toio Copy a block of data into I/O memory
Same here.
> - * @dst: The (I/O memory) destination for the copy
> - * @src: The (RAM) source for the data
> - * @count: The number of bytes to copy
> + * @addr: The (I/O memory) destination for the copy
> + * @buffer: The (RAM) source for the data
> + * @size: The number of bytes to copy
> *
> * Copy a block of data to I/O memory.
> */
>
If you would fix the above, you can also add:
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
thanks.
--
~Randy
prev parent reply other threads:[~2020-04-22 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:29 [PATCH] io: correct documentation mismatches for io memcpy Wang Wenhu
2020-04-22 16:42 ` Randy Dunlap [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=4b0a80ed-a639-c8c0-e6c3-01ba3266b7de@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=kernel@vivo.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wenhu.wang@vivo.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;
as well as URLs for NNTP newsgroup(s).