From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
roopa@nvidia.com, idosch@nvidia.com, stephen@networkplumber.org,
dsahern@kernel.org
Subject: Re: [PATCH iproute2] MAINTAINERS: update bridge entry
Date: Mon, 07 Apr 2025 18:20:32 +0000 [thread overview]
Message-ID: <174405003250.1220282.3145051055620556802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250405102504.219970-1-razor@blackwall.org>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Sat, 5 Apr 2025 13:25:04 +0300 you wrote:
> Sync with the kernel and update the bridge entry with the current bridge
> maintainers. Roopa decided to withdraw and Ido has agreed to step in.
>
> Link: https://lore.kernel.org/netdev/20250314100631.40999-1-razor@blackwall.org/
> CC: Roopa Prabhu <roopa@nvidia.com>
> CC: Ido Schimmel <idosch@nvidia.com>
> CC: Stephen Hemminger <stephen@networkplumber.org>
> CC: David Ahern <dsahern@kernel.org>
> Signed-off-by: Nikolay Aleksandrov <razor@blackwall.org>
>
> [...]
Here is the summary with links:
- [iproute2] MAINTAINERS: update bridge entry
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=c498efe79ba9
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-04-07 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 10:25 [PATCH iproute2] MAINTAINERS: update bridge entry Nikolay Aleksandrov
2025-04-07 8:30 ` Ido Schimmel
2025-04-07 18:20 ` 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=174405003250.1220282.3145051055620556802.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=stephen@networkplumber.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.