From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
corbet@lwn.net, vladimir.oltean@nxp.com, willemb@google.com,
sdf.kernel@gmail.com, ecree.xilinx@gmail.com,
jesse.brandeburg@intel.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] docs: net: updates for old and cobwebbed docs
Date: Wed, 27 May 2026 07:48:39 -0700 [thread overview]
Message-ID: <20260527074839.7a78f1c2@kernel.org> (raw)
In-Reply-To: <72e0f118-5fa5-4ca7-b443-b472e7ba317d@infradead.org>
On Tue, 26 May 2026 19:39:47 -0700 Randy Dunlap wrote:
> On 5/26/26 6:15 PM, Jakub Kicinski wrote:
> > On Tue, 26 May 2026 17:51:45 -0700 Randy Dunlap wrote:
> >> It's in today's linux-next (20260526), line 1950 of
> >> include/linux/netdevice.h:
> >
> > linux-next is useful, but we try not to merge broken code, not just
> > notice it after the fact. So it'd be great if the fix made its way
> > to Linus and therefore propagate to subsystem -next trees, not just
> > linux-next.
>
> OK. I don't quite know what you mean by that, but I just checked the
> current net-next tree and it's still there at line 1950.
Sorry, I'm talking about the regression in the kernel-doc _script_
which was recently fixed, and which hid the "excess kdoc" warnings.
I'm guessing that it's fixed now in linux-next.
That's why you see the warning in linux-next and I don't in networking
trees. What I was trying to argue was that that script fix should be
sent to Linus, not sit in linux-next.
prev parent reply other threads:[~2026-05-27 14:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 16:01 [PATCH net-next 00/10] docs: net: updates for old and cobwebbed docs Jakub Kicinski
2026-05-26 16:01 ` [PATCH net-next 01/10] docs: net: netdevices: small fixes and clarifications Jakub Kicinski
2026-05-26 22:12 ` Stanislav Fomichev
2026-05-26 16:01 ` [PATCH net-next 02/10] docs: net: fix minor issues with driver guide Jakub Kicinski
2026-05-26 16:01 ` [PATCH net-next 03/10] docs: net: statistics: fix kernel-internal stats list Jakub Kicinski
2026-05-26 16:01 ` [PATCH net-next 04/10] docs: net: update devmem code examples Jakub Kicinski
2026-05-26 22:17 ` Stanislav Fomichev
2026-05-26 16:01 ` [PATCH net-next 05/10] docs: net: fix minor issues with the NAPI guide Jakub Kicinski
2026-05-26 16:01 ` [PATCH net-next 06/10] docs: net: refresh netdev feature guidance Jakub Kicinski
2026-05-26 18:41 ` Maxime Chevallier
2026-05-26 22:35 ` Jakub Kicinski
2026-05-27 7:53 ` Maxime Chevallier
2026-05-26 16:01 ` [PATCH net-next 07/10] docs: net: fix minor issues with checksum offloads Jakub Kicinski
2026-05-26 16:01 ` [PATCH net-next 08/10] docs: net: add Rx notes to the checksum guide Jakub Kicinski
2026-05-26 18:56 ` Willem de Bruijn
2026-05-26 16:01 ` [PATCH net-next 09/10] docs: net: render the checksum comment in checksum-offloads.rst Jakub Kicinski
2026-05-26 18:56 ` Willem de Bruijn
2026-05-26 16:01 ` [PATCH net-next 10/10] docs: net: fix minor issues with segmentation offloads Jakub Kicinski
2026-05-26 18:48 ` [PATCH net-next 00/10] docs: net: updates for old and cobwebbed docs Randy Dunlap
2026-05-26 22:37 ` Jakub Kicinski
2026-05-26 22:40 ` Jakub Kicinski
2026-05-27 0:51 ` Randy Dunlap
2026-05-27 1:15 ` Jakub Kicinski
2026-05-27 2:39 ` Randy Dunlap
2026-05-27 14:48 ` Jakub Kicinski [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=20260527074839.7a78f1c2@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sdf.kernel@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=willemb@google.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