Netdev List
 help / color / mirror / Atom feed
From: "Austin, Alex (DCCG)" <alex.austin@amd.com>
To: Arnav Kapoor <kapoorarnav43@gmail.com>,
	Edward Cree <ecree.xilinx@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-net-drivers@amd.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] sfc: fix stale kernel-doc member names in net_driver.h
Date: Thu, 8 Oct 2026 16:33:28 +0100	[thread overview]
Message-ID: <e8aa32c6-2b9d-4cf0-9840-1d7b252b0792@amd.com> (raw)
In-Reply-To: <20261007175338.28683-1-kapoorarnav43@gmail.com>


On 07/10/2026 18:53, Arnav Kapoor wrote:
> Several kernel-doc comments in net_driver.h describe struct members that
> have since been renamed or removed, and the EFX_MAX_FRAME_LEN() comment
> is separated from the macro by the EFX_FRAME_PAD define. kernel-doc
> reports:
>
>   Excess struct member 'state' description in 'efx_channel'
>   Excess struct member 'state_lock' description in 'efx_channel'
>   Excess struct member 'indir_table' description in 'efx_rss_context'
>   Excess struct member 'irq_rx_mod_step_us' description in 'efx_nic'
>   Excess struct member 'tx_queue' description in 'efx_nic'
>   Excess struct member 'rx_queue' description in 'efx_nic'
>   Excess struct member 'extra_channel_types' description in 'efx_nic'
>   expecting prototype for EFX_MAX_FRAME_LEN(). Prototype was for
>   EFX_FRAME_PAD() instead
>
> along with "not described" warnings for the renamed members.
>
> Fix the member names to match the structs, drop the entries for members
> that no longer exist, and move the EFX_FRAME_PAD define above the
> EFX_MAX_FRAME_LEN() comment, documenting its @mtu parameter.
>
> kernel-doc -Wall also reports three members that are not described
> because nothing in the driver uses them any more, so remove them rather
> than document them:
>
>   - efx_channel::busy_poll_state, left behind when commit e7fe9491261e
>     ("sfc: get rid of custom busy polling code") removed its users.
>     @state and @state_lock above were its old kernel-doc entries.
>   - efx_tx_queue::flush_outstanding, only used by the Falcon/Siena
>     flush code, which commit 36ff6393292d ("sfc: Move Siena specific
>     files") moved into siena/ with its own copy of the struct.
>   - efx_rx_queue::min_overfill, whose kernel-doc entry and only
>     assignment were removed by commit ecc910f520ba ("sfc: Make the dmaq
>     size a run-time setting (rather than compile-time)").
>
> The warnings were found with scripts/kernel-doc -Wall. I don't have sfc
> hardware; this is compile-tested only.
>
> No functional change.
>
> Assisted-by: LLM
> Signed-off-by: Arnav Kapoor <kapoorarnav43@gmail.com>
> ---
> Changes in v2:
> - Remove busy_poll_state, flush_outstanding and min_overfill, which are
>   unused, instead of leaving them undocumented (Simon)
> - Use the Assisted-by format from coding-assistants.rst
>
> net_driver.h has further members with no kernel-doc description,
> mostly in struct efx_nic and struct efx_nic_type. Those are in use, so
> I'll document them in a separate patch.
>
> W=1 build of drivers/net/ethernet/sfc/ shows no new warnings.
>
> v1: https://lore.kernel.org/all/20261003055443.144554-1-kapoorarnav43@gmail.com/
>
>  drivers/net/ethernet/sfc/net_driver.h | 21 +++++++--------------
>  1 file changed, 7 insertions(+), 14 deletions(-)
>

Reviewed-by: Alex Austin <alex.austin@amd.com>


  reply	other threads:[~2026-10-08 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 17:53 [PATCH net-next v2] sfc: fix stale kernel-doc member names in net_driver.h Arnav Kapoor
2026-10-08 15:33 ` Austin, Alex (DCCG) [this message]
2026-10-09 16:50 ` Simon Horman

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=e8aa32c6-2b9d-4cf0-9840-1d7b252b0792@amd.com \
    --to=alex.austin@amd.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kapoorarnav43@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --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