From: patchwork-bot+netdevbpf@kernel.org
To: Amit Cohen <amcohen@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
stephen@networkplumber.org, razor@blackwall.org,
mlxsw@nvidia.com, roopa@nvidia.com
Subject: Re: [PATCH iproute2-next v2 0/8] Extend flush command to support VXLAN attributes
Date: Fri, 20 Oct 2023 15:50:24 +0000 [thread overview]
Message-ID: <169781702408.13692.10637906256677459210.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231017105532.3563683-1-amcohen@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 17 Oct 2023 13:55:24 +0300 you wrote:
> The merge commit f84e3f8cced9 ("Merge branch 'bridge-fdb-flush' into next")
> added support for fdb flushing.
>
> The kernel was extended to support flush for VXLAN device, so the
> "bridge fdb flush" command should support new attributes.
>
> Add support for flushing FDB entries based on the following:
> * Source VNI
> * Nexthop ID
> * Destination VNI
> * Destination Port
> * Destination IP
> * 'router' flag
>
> [...]
Here is the summary with links:
- [iproute2-next,v2,1/8] bridge: fdb: rename some variables to contain 'brport'
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=c1904631bb84
- [iproute2-next,v2,2/8] bridge: fdb: support match on source VNI in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=69b0310e82c6
- [iproute2-next,v2,3/8] bridge: fdb: support match on nexthop ID in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=f3c34db4be1d
- [iproute2-next,v2,4/8] bridge: fdb: support match on destination VNI in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=9107073a78e4
- [iproute2-next,v2,5/8] bridge: fdb: support match on destination port in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=1b429388aaa3
- [iproute2-next,v2,6/8] bridge: fdb: support match on destination IP in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=994bf05ee265
- [iproute2-next,v2,7/8] bridge: fdb: support match on [no]router flag in flush command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=958eecd2d05a
- [iproute2-next,v2,8/8] man: bridge: add a note about using 'master' and 'self' with flush
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=734a82a15e1a
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-10-20 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 10:55 [PATCH iproute2-next v2 0/8] Extend flush command to support VXLAN attributes Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 1/8] bridge: fdb: rename some variables to contain 'brport' Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 2/8] bridge: fdb: support match on source VNI in flush command Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 3/8] bridge: fdb: support match on nexthop ID " Amit Cohen
2023-10-17 12:53 ` Nikolay Aleksandrov
2023-10-17 10:55 ` [PATCH iproute2-next v2 4/8] bridge: fdb: support match on destination VNI " Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 5/8] bridge: fdb: support match on destination port " Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 6/8] bridge: fdb: support match on destination IP " Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 7/8] bridge: fdb: support match on [no]router flag " Amit Cohen
2023-10-17 10:55 ` [PATCH iproute2-next v2 8/8] man: bridge: add a note about using 'master' and 'self' with flush Amit Cohen
2023-10-20 15: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=169781702408.13692.10637906256677459210.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=dsahern@gmail.com \
--cc=mlxsw@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 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).