From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Karl Mehltretter <kmehltretter@gmail.com>,
corbet@lwn.net
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
mchehab@kernel.org, skhan@linuxfoundation.org, horms@kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net_shaper: fix kernel-doc rendering
Date: Fri, 25 Sep 2026 12:01:52 -0700 [thread overview]
Message-ID: <20260925120152.09ef180c@kernel.org> (raw)
In-Reply-To: <d461b048-b08a-4bbe-b5e7-60ed6686ab52@infradead.org>
On Thu, 24 Sep 2026 16:13:05 -0700 Randy Dunlap wrote:
> > Here is the summary with links:
> > - [net-next,v2,1/2] net_shaper: fix kernel-doc list indentation
> > https://git.kernel.org/netdev/net-next/c/09b7c00d55a8
> > - [net-next,v2,2/2] docs: kerneldoc.py: preserve headings in kernel-doc output
> > (no matching commit)
> >
> > You are awesome, thank you!
>
> so these 2 patches are merged into net-next, which should be merged
> into mainline Linux at the next merge window (in the 2 weeks after
> Linux v7.3 is released).
>
> Patch 1/2 is in the current linux-next daily releases.
> However, patch 2/2 is not merged anywhere in linux-next AFAICT.
>
> I also would like to see patch 2/2 merged...
Sorry, maybe I should have called it out more explicitly instead of
expecting people to read the pw-bot reply. Yes, I only took the
networking change. I think it's easiest if Karl reposts the other one
for Jon to apply? (without tagging it for net-next of course)
prev parent reply other threads:[~2026-09-25 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 1:32 Karl Mehltretter
2026-08-15 1:32 ` [PATCH net-next v2 1/2] net_shaper: fix kernel-doc list indentation Karl Mehltretter
2026-08-16 17:13 ` Randy Dunlap
2026-08-15 1:32 ` [PATCH net-next v2 2/2] docs: kerneldoc.py: preserve headings in kernel-doc output Karl Mehltretter
2026-08-16 17:14 ` Randy Dunlap
2026-09-19 5:30 ` Karl Mehltretter
2026-08-17 21:00 ` [PATCH net-next v2 0/2] net_shaper: fix kernel-doc rendering patchwork-bot+netdevbpf
2026-09-24 23:13 ` Randy Dunlap
2026-09-25 19:01 ` 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=20260925120152.09ef180c@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®