From: patchwork-bot+linux-arm-msm@kernel.org
To: Jonathan McDowell <noodles@earth.li>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: Fix ADM driver kerneldoc markup
Date: Tue, 29 Dec 2020 20:15:33 +0000 [thread overview]
Message-ID: <160927293358.13751.12571363987977209630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201126184602.GA1008@earth.li>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 26 Nov 2020 18:46:02 +0000 you wrote:
> Update the kerneldoc function headers to fix build warnings:
>
> drivers/dma/qcom/qcom_adm.c:180: warning: Function parameter or member 'chan' not described in 'adm_free_chan'
> drivers/dma/qcom/qcom_adm.c:190: warning: Function parameter or member 'burst' not described in 'adm_get_blksize'
> drivers/dma/qcom/qcom_adm.c:466: warning: Function parameter or member 'chan' not described in 'adm_terminate_all'
> drivers/dma/qcom/qcom_adm.c:466: warning: Excess function parameter 'achan' description in 'adm_terminate_all'
> drivers/dma/qcom/qcom_adm.c:503: warning: Function parameter or member 'achan' not described in 'adm_start_dma'
>
> [...]
Here is the summary with links:
- dmaengine: qcom: Fix ADM driver kerneldoc markup
https://git.kernel.org/qcom/c/4facce4c1263
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-29 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 18:46 [PATCH] dmaengine: qcom: Fix ADM driver kerneldoc markup Jonathan McDowell
2020-12-11 13:36 ` Vinod Koul
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293358.13751.12571363987977209630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=noodles@earth.li \
/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).