From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, Leszek Pepiak <leszek.pepiak@intel.com>
Subject: Re: [PATCH net-next] iavf: fix kernel-doc comment style in ethtool ops
Date: Wed, 8 Apr 2026 14:13:53 -0700 [thread overview]
Message-ID: <ada0ab49-842a-4a7e-9854-0a997987c0e5@intel.com> (raw)
In-Reply-To: <20260403054321.3791392-1-aleksandr.loktionov@intel.com>
On 4/2/2026 10:43 PM, Aleksandr Loktionov wrote:
> From: Leszek Pepiak <leszek.pepiak@intel.com>
>
> iavf_get_channels() and iavf_set_channels() use the legacy `**/`
> comment terminator and embed the return description in the body text.
> Convert to proper kernel-doc style: single `*/` terminator and an
> explicit `Return:` section.
My inexact check of iavf shows this:
grep '\*\*/' drivers/net/ethernet/intel/iavf/* | wc -l
248
scripts/kernel-doc -none -Wreturn drivers/net/ethernet/intel/iavf/* 2>&1
| wc -l
336
Since this is not in the context of other changes and this resolves <1%
of the issues, this doesn't seem like much of a net gain. If we're
looking to resolve kernel-doc warnings perhaps fixing 1 file at a time?
Bonus points if we can remove boilerplate ones :)
Thanks,
Tony
> Signed-off-by: Leszek Pepiak <leszek.pepiak@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
>
> ---
> drivers/net/ethernet/intel/iavf/iavf_ethtool.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_ethtool.c b/drivers/net/ethernet/intel/iavf/iavf_ethtool.c
> index 8188dd4..425acbb 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_ethtool.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_ethtool.c
> @@ -1846,13 +1846,13 @@ static int iavf_get_rxnfc(struct net_device *netdev, struct ethtool_rxnfc *cmd,
> return ret;
> }
> /**
> - * iavf_get_channels: get the number of channels supported by the device
> + * iavf_get_channels - get the number of channels supported by the device
> * @netdev: network interface device structure
> * @ch: channel information structure
> *
> * For the purposes of our device, we only use combined channels, i.e. a tx/rx
> * queue pair. Report one extra channel to match our "other" MSI-X vector.
> - **/
> + */
> static void iavf_get_channels(struct net_device *netdev,
> struct ethtool_channels *ch)
> {
> @@ -1873,14 +1873,15 @@ static void iavf_get_channels(struct net_device *netdev,
> }
>
> /**
> - * iavf_set_channels: set the new channel count
> + * iavf_set_channels - set the new channel count
> * @netdev: network interface device structure
> * @ch: channel information structure
> *
> * Negotiate a new number of channels with the PF then do a reset. During
> - * reset we'll realloc queues and fix the RSS table. Returns 0 on success,
> - * negative on failure.
> - **/
> + * reset we'll realloc queues and fix the RSS table.
> + *
> + * Return: 0 on success, negative on failure.
> + */
> static int iavf_set_channels(struct net_device *netdev,
> struct ethtool_channels *ch)
> {
prev parent reply other threads:[~2026-04-08 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 5:43 [PATCH net-next] iavf: fix kernel-doc comment style in ethtool ops Aleksandr Loktionov
2026-04-03 8:09 ` [Intel-wired-lan] " Paul Menzel
2026-04-03 16:57 ` Joe Damato
2026-04-08 21:13 ` Tony Nguyen [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=ada0ab49-842a-4a7e-9854-0a997987c0e5@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@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