From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, corbet@lwn.net, donald.hunter@gmail.com,
mchehab+huawei@kernel.org, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kory.maincent@bootlin.com
Subject: Re: [PATCH net-next] doc: mptcp: fix Netlink specs link
Date: Thu, 11 Sep 2025 01:50:08 +0000 [thread overview]
Message-ID: <175755540824.1625707.41414592055811812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909-net-next-mptcp-pm-link-v1-1-0f1c4b8439c6@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 09 Sep 2025 19:46:09 +0200 you wrote:
> The Netlink specs RST files are no longer generated inside the source
> tree.
>
> In other words, the path to mptcp_pm.rst has changed, and needs to be
> updated to the new location.
>
> Fixes: 1ce4da3dd99e ("docs: use parser_yaml extension to handle Netlink specs")
> Reported-by: Kory Maincent <kory.maincent@bootlin.com>
> Closes: https://lore.kernel.org/20250828185037.07873d04@kmaincent-XPS-13-7390
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next] doc: mptcp: fix Netlink specs link
https://git.kernel.org/netdev/net-next/c/1f24a2409745
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:[~2025-09-11 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 17:46 [PATCH net-next] doc: mptcp: fix Netlink specs link Matthieu Baerts (NGI0)
2025-09-11 1: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=175755540824.1625707.41414592055811812.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mptcp@lists.linux.dev \
--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 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).