From: patchwork-bot+netdevbpf@kernel.org
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mchehab@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, horms@kernel.org,
rdunlap@infradead.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: Mon, 17 Aug 2026 21:00:10 +0000 [thread overview]
Message-ID: <178700041013.1735578.3422132046076853057.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1786751700.git.kmehltretter@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 15 Aug 2026 03:32:27 +0200 you wrote:
> The net_shaper_ops documentation contains a malformed ReST list and
> exposes a kerneldoc.py title-context bug which drops valid headings.
> Fix the list first because the parser correction makes it visible. The
> parser fix also restores three Xe DRM RAS headings already in mainline.
>
> Tested with Sphinx 9.1.0:
>
> [...]
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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-17 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 1:32 [PATCH net-next v2 0/2] net_shaper: fix kernel-doc rendering 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-08-17 21:00 ` 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=178700041013.1735578.3422132046076853057.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kmehltretter@gmail.com \
--cc=kuba@kernel.org \
--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 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.