From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
bpf@vger.kernel.org, stephen@networkplumber.org,
dsahern@kernel.org, willemb@google.com, ast@kernel.org
Subject: Re: [PATCH net-next v2] docs: netdev: fix iproute2 process documentation
Date: Tue, 10 Nov 2026 02:54:54 +0000 [thread overview]
Message-ID: <179427929417.3612825.2487623260094392811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105184510.3230744-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Nov 2026 13:44:51 -0500 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> The instructions on sending patches to iproute2 span both netdev and
> bpf docs, contain outdated references and miss some instructions.
> Address this:
>
> - Move all info to maintainer-netdev
> - Add a link in bpf_devel_QA to this location
> - Update URLs to git repositories
> - Update URLs to patchwork instance and delegates
> - Update subject prefix rules
> - Add suggestion to Cc: maintainers
> - Add pointer to iproute2 MAINTAINERS
> - Add pointer to iproute2 README.devel
>
> [...]
Here is the summary with links:
- [net-next,v2] docs: netdev: fix iproute2 process documentation
https://git.kernel.org/netdev/net/c/c597eb68599e
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-11-10 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 18:44 [PATCH net-next v2] docs: netdev: fix iproute2 process documentation Willem de Bruijn
2026-11-10 2:54 ` 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=179427929417.3612825.2487623260094392811.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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