From: Vinod Koul <vkoul@kernel.org>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: std_dma40: fix kernel-doc warnings and spelling
Date: Thu, 21 Dec 2023 21:59:58 +0530 [thread overview]
Message-ID: <170317619891.683420.428561244511510954.b4-ty@kernel.org> (raw)
In-Reply-To: <20231218060834.19222-1-rdunlap@infradead.org>
On Sun, 17 Dec 2023 22:08:34 -0800, Randy Dunlap wrote:
> Correct kernel-doc warnings as reported by kernel test robot:
>
> ste_dma40.c:57: warning: Excess struct member 'dev_tx' description in 'stedma40_platform_data'
> ste_dma40.c:57: warning: Excess struct member 'dev_rx' description in 'stedma40_platform_data'
>
> Correct spellos as reported by codespell.
>
> [...]
Applied, thanks!
[1/1] dmaengine: std_dma40: fix kernel-doc warnings and spelling
commit: 71a5197e2b872afeef8ade3099ffc4050466b542
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-12-21 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 6:08 Randy Dunlap
2023-12-20 11:24 ` Linus Walleij
2023-12-21 16:29 ` 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=170317619891.683420.428561244511510954.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®