From: patchwork-bot+linux-arm-msm@kernel.org
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] kernel-doc and MAINTAINERS clean-up
Date: Sun, 04 Apr 2021 18:10:11 +0000 [thread overview]
Message-ID: <161755981179.6823.1282421826121358216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210327065642.11969-1-lukas.bulwahn@gmail.com>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Sat, 27 Mar 2021 07:56:40 +0100 you wrote:
> Roughly 900 warnings of about 21.000 kernel-doc warnings in the kernel tree
> warn with 'cannot understand function prototype:', i.e., the kernel-doc parser
> cannot parse the function's signature. The majority, about 600 cases of those,
> are just struct definitions following the kernel-doc description. Further,
> spot-check investigations suggest that the authors of the specific kernel-doc
> descriptions simply were not aware that the general format for a kernel-doc
> description for a structure requires to prefix the struct name with the keyword
> 'struct', as in 'struct struct_name - Brief description.'. Details on
> kernel-doc are at the Link below.
>
> [...]
Here is the summary with links:
- [1/2] MAINTAINERS: add another entry for ARM/QUALCOMM SUPPORT
https://git.kernel.org/qcom/c/99d52c872d34
- [2/2] soc: qcom: address kernel-doc warnings
https://git.kernel.org/qcom/c/8058dfa05ab7
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:[~2021-04-04 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 6:56 [PATCH 0/2] kernel-doc and MAINTAINERS clean-up Lukas Bulwahn
2021-03-27 6:56 ` [PATCH 1/2] MAINTAINERS: add another entry for ARM/QUALCOMM SUPPORT Lukas Bulwahn
2021-03-27 6:56 ` [PATCH 2/2] soc: qcom: address kernel-doc warnings Lukas Bulwahn
2021-04-04 18:10 ` 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=161755981179.6823.1282421826121358216.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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