From: patchwork-bot+netdevbpf@kernel.org
To: Loktionov@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Aleksandr <aleksandr.loktionov@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org, leszek.pepiak@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] iavf: fix kernel-doc comment style in iavf_ethtool.c
Date: Fri, 10 Apr 2026 23:10:23 +0000 [thread overview]
Message-ID: <177586262379.2678602.4461794362716512859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260409093020.3808687-1-aleksandr.loktionov@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 Apr 2026 11:30:20 +0200 you wrote:
> iavf_ethtool.c contains 31 kernel-doc comment blocks using the legacy
> `**/` terminator instead of the correct single `*/`. Two function
> headers also use a colon separator (`iavf_get_channels:`,
> `iavf_set_channels:`) instead of the ` - ` dash required by kernel-doc.
>
> Additionally several comments embed their return-value descriptions in
> the body paragraph, producing `scripts/kernel-doc -Wreturn` warnings.
> Void functions that incorrectly say "Returns ..." are also rephrased.
>
> [...]
Here is the summary with links:
- [net-next,v2] iavf: fix kernel-doc comment style in iavf_ethtool.c
https://git.kernel.org/netdev/net-next/c/3f3a2aefbc66
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-04-10 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 9:30 [Intel-wired-lan] [PATCH net-next v2] iavf: fix kernel-doc comment style in iavf_ethtool.c Aleksandr Loktionov
2026-04-09 12:35 ` Breno Leitao
2026-04-10 17:53 ` Joe Damato
2026-04-10 23:10 ` 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=177586262379.2678602.4461794362716512859.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Loktionov@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=leszek.pepiak@intel.com \
--cc=netdev@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