From: Simon Horman <horms@kernel.org>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: 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>,
netdev@vger.kernel.org, linux-net-drivers@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] sfc: fix stale kernel-doc member names in net_driver.h
Date: Wed, 7 Oct 2026 16:22:05 +0100 [thread overview]
Message-ID: <20261007152205.GU83879@horms.kernel.org> (raw)
In-Reply-To: <20261003055443.144554-1-kapoorarnav43@gmail.com>
On Sat, Oct 03, 2026 at 11:24:41AM +0530, 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.
>
> No functional change.
>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Arnav Kapoor <kapoorarnav43@gmail.com>
> ---
> Comment-only change (plus moving a #define above the comment), checked
> with scripts/kernel-doc; W=1 build of drivers/net/ethernet/sfc/ shows no
> new warnings.
>
> drivers/net/ethernet/sfc/net_driver.h | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/sfc/net_driver.h b/drivers/net/ethernet/sfc/net_driver.h
> index 3964b2c56609..76b48f96ec62 100644
> --- a/drivers/net/ethernet/sfc/net_driver.h
> +++ b/drivers/net/ethernet/sfc/net_driver.h
> @@ -467,8 +467,6 @@ enum efx_sync_events_state {
> * @irq_moderation_us: IRQ moderation value (in microseconds)
> * @napi_dev: Net device used with NAPI
> * @napi_str: NAPI control structure
> - * @state: state for NAPI vs busy polling
> - * @state_lock: lock protecting @state
Hi Arnav,
I agree that neither state nor state_lock exist in struct efx_channel.
But while checking that I noticed that it seems the documentation
for @busy_poll_state is missing.
Could you ask your AI friend to audit that aspect too?
> * @eventq: Event queue buffer
> * @eventq_mask: Event queue pointer mask
> * @eventq_read_ptr: Event queue read pointer
...
prev parent reply other threads:[~2026-10-07 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 5:54 [PATCH net-next] sfc: fix stale kernel-doc member names in net_driver.h Arnav Kapoor
2026-10-07 15:22 ` Simon Horman [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=20261007152205.GU83879@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@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