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,
petrm@nvidia.com
Subject: Re: [PATCH iproute2-next] bridge: fdb: Add support for FDB activity notification control
Date: Mon, 28 Jul 2025 17:10:19 +0000 [thread overview]
Message-ID: <175372261974.782645.4776959441968068820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250717130509.470850-1-idosch@nvidia.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 17 Jul 2025 16:05:09 +0300 you wrote:
> Add support for FDB activity notification control [1].
>
> Users can use this to enable activity notifications on a new FDB entry
> that was learned on an ES (Ethernet Segment) peer and mark it as locally
> inactive:
>
> # bridge fdb add 00:11:22:33:44:55 dev bond1 master static activity_notify inactive
> $ bridge -d fdb get 00:11:22:33:44:55 br br1
> 00:11:22:33:44:55 dev bond1 activity_notify inactive master br1 static
> $ bridge -d -j -p fdb get 00:11:22:33:44:55 br br1
> [ {
> "mac": "00:11:22:33:44:55",
> "ifname": "bond1",
> "activity_notify": true,
> "inactive": true,
> "flags": [ ],
> "master": "br1",
> "state": "static"
> } ]
>
> [...]
Here is the summary with links:
- [iproute2-next] bridge: fdb: Add support for FDB activity notification control
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=e041178ba6bc
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-07-28 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 13:05 [PATCH iproute2-next] bridge: fdb: Add support for FDB activity notification control Ido Schimmel
2025-07-17 13:14 ` Nikolay Aleksandrov
2025-07-28 17:10 ` 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=175372261974.782645.4776959441968068820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--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.