From: Olivier dautricourt <olivierdautricourt@gmail.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: sr@denx.de, vkoul@kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] dmaengine: altera: Fix kernel-doc
Date: Thu, 26 May 2022 22:15:16 +0200 [thread overview]
Message-ID: <Yo/f1F5wf1Tpaqoi@olivier-3493erg> (raw)
In-Reply-To: <20220525093313.52749-1-jiapeng.chong@linux.alibaba.com>
On Wed, May 25, 2022 at 05:33:13PM +0800, Jiapeng Chong wrote:
> Fix the following W=1 kernel warnings:
>
> drivers/dma/altera-msgdma.c:927: warning: expecting prototype for
> msgdma_dma_remove(). Prototype was for msgdma_remove() instead.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> drivers/dma/altera-msgdma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/altera-msgdma.c b/drivers/dma/altera-msgdma.c
> index 6f56dfd375e3..bdaac5d62a04 100644
> --- a/drivers/dma/altera-msgdma.c
> +++ b/drivers/dma/altera-msgdma.c
> @@ -918,7 +918,7 @@ static int msgdma_probe(struct platform_device *pdev)
> }
>
> /**
> - * msgdma_dma_remove - Driver remove function
> + * msgdma_remove() - Driver remove function
> * @pdev: Pointer to the platform_device structure
> *
> * Return: Always '0'
> --
> 2.20.1.7.g153144c
>
Hello, thanks for reporting.
I notice now that another doc entry is misnamed:
drivers/dma/altera-msgdma.c:758: warning: expecting prototype for
msgdma_chan_remove(). Prototype was for msgdma_dev_remove() instead
Is it possible for you to fix this aswell ?
I also suggest using the full name of the driver in the commit message:
dmaengine: altera-msgdma: ...
Kr,
Olivier
next prev parent reply other threads:[~2022-05-26 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 9:33 [PATCH] dmaengine: altera: Fix kernel-doc Jiapeng Chong
2022-05-26 20:15 ` Olivier dautricourt [this message]
2022-07-06 5:37 ` Vinod Koul
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=Yo/f1F5wf1Tpaqoi@olivier-3493erg \
--to=olivierdautricourt@gmail.com \
--cc=abaci@linux.alibaba.com \
--cc=dmaengine@vger.kernel.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sr@denx.de \
--cc=vkoul@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