From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Frank Li <Frank.Li@nxp.com>
Cc: imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dmaengine: fsl-dpaa2-qdma: Fix kernel-doc check warning
Date: Thu, 25 Apr 2024 14:47:30 +0530 [thread overview]
Message-ID: <171403665042.79852.486189247427998901.b4-ty@kernel.org> (raw)
In-Reply-To: <20240418185851.3221726-1-Frank.Li@nxp.com>
On Thu, 18 Apr 2024 14:58:49 -0400, Frank Li wrote:
> Fix all kernel-doc warnings under drivers/dma/fsl-dpaa2-qdma.
>
> ./scripts/kernel-doc -v -none drivers/dma/fsl-dpaa2-qdma/*
> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:262: warning: Function parameter or struct member 'queue_idx' not described in 'dpdmai_set_rx_queue'
> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:339: warning: Excess function parameter 'fqid' description in 'dpdmai_get_tx_queue'
> ...
>
> [...]
Applied, thanks!
[1/1] dmaengine: fsl-dpaa2-qdma: Fix kernel-doc check warning
commit: 39def87bc7cae8ddfd6703051fc59931f152a2cb
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-04-25 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 18:58 [PATCH 1/1] dmaengine: fsl-dpaa2-qdma: Fix kernel-doc check warning Frank Li
2024-04-25 9:17 ` Vinod Koul [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=171403665042.79852.486189247427998901.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).