From: patchwork-bot+netdevbpf@kernel.org
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: ecree.xilinx@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, 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: Tue, 13 Oct 2026 10:50:04 +0000 [thread overview]
Message-ID: <179188860427.217011.7064100465923147742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007175338.28683-1-kapoorarnav43@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 7 Oct 2026 23:23:34 +0530 you 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
>
> [...]
Here is the summary with links:
- [net-next,v2] sfc: fix stale kernel-doc member names in net_driver.h
https://git.kernel.org/netdev/net-next/c/32a8010d2c30
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-10-13 10:50 UTC|newest]
Thread overview: 4+ 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)
2026-10-09 16:50 ` Simon Horman
2026-10-13 10: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=179188860427.217011.7064100465923147742.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.