From: Randy Dunlap <rdunlap@infradead.org>
To: Yang Li <yang.lee@linux.alibaba.com>,
mporter@kernel.crashing.org, alex.bou9@gmail.com
Cc: linux-kernel@vger.kernel.org, Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] rapidio/tsi721: Fix some kernel-doc comments
Date: Wed, 26 Jul 2023 19:43:42 -0700 [thread overview]
Message-ID: <4597bdb9-8a90-6d4e-3904-161fffb87350@infradead.org> (raw)
In-Reply-To: <20230727020840.87684-1-yang.lee@linux.alibaba.com>
On 7/26/23 19:08, Yang Li wrote:
> Fix some kernel-doc comments to silence the warnings:
>
> drivers/rapidio/devices/tsi721.c:215: warning: Function parameter or member 'data' not described in 'tsi721_cread_dma'
> drivers/rapidio/devices/tsi721.c:215: warning: Excess function parameter 'val' description in 'tsi721_cread_dma'
> drivers/rapidio/devices/tsi721.c:238: warning: Function parameter or member 'data' not described in 'tsi721_cwrite_dma'
> drivers/rapidio/devices/tsi721.c:238: warning: Excess function parameter 'val' description in 'tsi721_cwrite_dma'
> drivers/rapidio/devices/tsi721.c:2548: warning: Function parameter or member 'attr' not described in 'tsi721_query_mport'
> drivers/rapidio/devices/tsi721.c:2548: warning: Excess function parameter 'mbox' description in 'tsi721_query_mport'
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5997
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/rapidio/devices/tsi721.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/rapidio/devices/tsi721.c b/drivers/rapidio/devices/tsi721.c
> index 83323c3d10af..3e67001702bc 100644
> --- a/drivers/rapidio/devices/tsi721.c
> +++ b/drivers/rapidio/devices/tsi721.c
> @@ -205,7 +205,7 @@ static int tsi721_maint_dma(struct tsi721_device *priv, u32 sys_size,
> * @hopcount: Number of hops to target device
> * @offset: Offset into configuration space
> * @len: Length (in bytes) of the maintenance transaction
> - * @val: Location to be read into
> + * @data: Location to be read into
> *
> * Generates a RapidIO maintenance read transaction.
> * Returns %0 on success and %-EINVAL or %-EFAULT on failure.
> @@ -228,7 +228,7 @@ static int tsi721_cread_dma(struct rio_mport *mport, int index, u16 destid,
> * @hopcount: Number of hops to target device
> * @offset: Offset into configuration space
> * @len: Length (in bytes) of the maintenance transaction
> - * @val: Value to be written
> + * @data: Value to be written
> *
> * Generates a RapidIO maintenance write transaction.
> * Returns %0 on success and %-EINVAL or %-EFAULT on failure.
> @@ -2539,7 +2539,7 @@ static int tsi721_messages_init(struct tsi721_device *priv)
> /**
> * tsi721_query_mport - Fetch inbound message from the Tsi721 MSG Queue
> * @mport: Master port implementing the Inbound Messaging Engine
> - * @mbox: Inbound mailbox number
> + * @attr: RIO mport device attributes
> *
> * Returns pointer to the message on success or NULL on failure.
> */
--
~Randy
prev parent reply other threads:[~2023-07-27 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 2:08 Yang Li
2023-07-27 2:43 ` 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=4597bdb9-8a90-6d4e-3904-161fffb87350@infradead.org \
--to=rdunlap@infradead.org \
--cc=abaci@linux.alibaba.com \
--cc=alex.bou9@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=yang.lee@linux.alibaba.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
all inboxes | Powered by JetHome®