From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hawk@kernel.org, ilias.apalodimas@linaro.org,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] page_pool: fix &page_pool_params kdoc issues
Date: Tue, 28 May 2024 00:20:30 +0000 [thread overview]
Message-ID: <171685563085.6024.16419471197715039412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240524112859.2757403-1-aleksander.lobakin@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 24 May 2024 13:28:59 +0200 you wrote:
> After the tagged commit, @netdev got documented twice and the kdoc
> script didn't notice that. Remove the second description added later
> and move the initial one according to the field position.
>
> After merging commit 5f8e4007c10d ("kernel-doc: fix
> struct_group_tagged() parsing"), kdoc requires to describe struct
> groups as well. &page_pool_params has 2 struct groups which
> generated new warnings, describe them to resolve this.
>
> [...]
Here is the summary with links:
- [net] page_pool: fix &page_pool_params kdoc issues
https://git.kernel.org/netdev/net/c/266aa3b4812e
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:[~2024-05-28 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 11:28 [PATCH net] page_pool: fix &page_pool_params kdoc issues Alexander Lobakin
2024-05-28 0:20 ` patchwork-bot+netdevbpf [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=171685563085.6024.16419471197715039412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.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