From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, wintera@linux.ibm.com,
twinkler@linux.ibm.com, linux-s390@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH v3 net-next] net/iucv: clean up iucv kernel-doc warnings
Date: Thu, 05 Feb 2026 04:50:18 +0000 [thread overview]
Message-ID: <177026701882.165764.4197190768444088497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203075248.1177869-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Feb 2026 23:52:48 -0800 you wrote:
> Fix numerous (many) kernel-doc warnings in iucv.[ch]:
>
> - convert function documentation comments to a common (kernel-doc) look,
> even for static functions (without "/**")
> - use matching parameter and parameter description names
> - use better wording in function descriptions (Jakub & AI)
> - remove duplicate kernel-doc comments from the header file (Jakub)
>
> [...]
Here is the summary with links:
- [v3,net-next] net/iucv: clean up iucv kernel-doc warnings
https://git.kernel.org/netdev/net-next/c/a34b0e4e21d6
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:[~2026-02-05 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 7:52 [PATCH v3 net-next] net/iucv: clean up iucv kernel-doc warnings Randy Dunlap
2026-02-03 9:39 ` Alexandra Winter
2026-02-03 18:30 ` Randy Dunlap
2026-02-05 4:40 ` Jakub Kicinski
2026-02-05 4:50 ` 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=177026701882.165764.4197190768444088497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.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