From: patchwork-bot+netdevbpf@kernel•org
To: Ido Schimmel <idosch@nvidia•com>
Cc: netdev@vger•kernel.org, dsahern@gmail•com,
stephen@networkplumber•org, razor@blackwall•org,
liuhangbin@gmail•com
Subject: Re: [PATCH iproute2-next 0/2] bridge: Add support for per-{Port, VLAN} neighbor suppression
Date: Tue, 25 Apr 2023 15:00:19 +0000 [thread overview]
Message-ID: <168243481986.8853.9982934533845896183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424160951.232878-1-idosch@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel•org>:
On Mon, 24 Apr 2023 19:09:49 +0300 you wrote:
> See kernel merge commit 25c800b21058 ("Merge branch
> 'bridge-neigh-suppression'") for background and motivation.
>
> Patch #1 adds support for a new "bridge vlan" option, "neigh_suppress".
>
> Patch #2 adds support for a new "bridge link" option,
> "neigh_vlan_suppress".
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] bridge: vlan: Add support for neigh_suppress option
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=5fe0aeb88427
- [iproute2-next,2/2] bridge: link: Add support for neigh_vlan_suppress option
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=9c7bdc9f3328
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:[~2023-04-25 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 16:09 [PATCH iproute2-next 0/2] bridge: Add support for per-{Port, VLAN} neighbor suppression Ido Schimmel
2023-04-24 16:09 ` [PATCH iproute2-next 1/2] bridge: vlan: Add support for neigh_suppress option Ido Schimmel
2023-04-25 6:47 ` Nikolay Aleksandrov
2023-04-24 16:09 ` [PATCH iproute2-next 2/2] bridge: link: Add support for neigh_vlan_suppress option Ido Schimmel
2023-04-25 6:48 ` Nikolay Aleksandrov
2023-04-25 15: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=168243481986.8853.9982934533845896183.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dsahern@gmail$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=liuhangbin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=razor@blackwall$(echo .)org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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