From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, Edward Cree <ecree.xilinx@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-net-drivers@amd.com
Subject: Re: [PATCH net-next] sfc: correct kernel-doc complaints
Date: Mon, 1 Dec 2025 14:45:43 -0800 [thread overview]
Message-ID: <20251201144543.26f845de@kernel.org> (raw)
In-Reply-To: <20251129220351.1980981-1-rdunlap@infradead.org>
On Sat, 29 Nov 2025 14:03:51 -0800 Randy Dunlap wrote:
> + * @port_id: port id (Ethernet address) if !CONFIG_SFC_SRIOV;
> + * for CONFIG_SFC_SRIOV, the VF port id
Thanks for the cleanup, but TBH this one sounds a little bit awkward.
Hopefully the SFC / AMD folks can suggest better wording. I'm dropping
this version from PW, I'm trying to wrap up netdev for 6.19..
--
pw-bot: cr
next prev parent reply other threads:[~2025-12-01 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 22:03 [PATCH net-next] sfc: correct kernel-doc complaints Randy Dunlap
2025-12-01 22:45 ` Jakub Kicinski [this message]
2025-12-05 17:19 ` Edward Cree
2025-12-05 20:02 ` Randy Dunlap
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=20251201144543.26f845de@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).