From: patchwork-bot+netdevbpf@kernel.org
To: Joachim Wiberg <troglobit@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
stephen@networkplumber.org, razor@blackwall.org
Subject: Re: [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port
Date: Sat, 12 Mar 2022 16:10:11 +0000 [thread overview]
Message-ID: <164710141170.15431.13449021992708210326.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309192316.2918792-1-troglobit@gmail.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 9 Mar 2022 20:23:09 +0100 you wrote:
> Hi,
>
> this patch set address a slight omission in controlling broadcast
> flooding per bridge port, which the bridge has had support for a good
> while now.
>
> v3:
> - Move bcast_flood option in manual files to before the mcast_flood
> option, instead of breaking the two mcast options. Unfortunately
> the other options are not alphabetically sorted, so this was the
> least worst option. (Stephen)
> - Add missing closing " for 'bridge mdb show' in bridge(8) SYNOPSIS
> v2:
> - Add bcast_flood also to ip/iplink_bridge_slave.c (Nik)
> - Update man page for ip-link(8) with new bcast_flood flag
> - Update mcast_flood in same man page slightly
> - Fix minor weird whitespace issues causing sudden line breaks
> v1:
> - Add bcast_flood to bridge/link.c
> - Update man page for bridge(8) with bcast_flood for brports
>
> [...]
Here is the summary with links:
- [iproute2-next,v3,1/7] bridge: support for controlling flooding of broadcast per port
(no matching commit)
- [iproute2-next,v3,2/7] man: bridge: document new bcast_flood flag for bridge ports
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=3b681cf9c75e
- [iproute2-next,v3,3/7] man: bridge: add missing closing " in bridge show mdb
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=909f0d510153
- [iproute2-next,v3,4/7] ip: iplink_bridge_slave: support for broadcast flooding
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=c354a434b1bf
- [iproute2-next,v3,5/7] man: ip-link: document new bcast_flood flag on bridge ports
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=b1c3ad848c1c
- [iproute2-next,v3,6/7] man: ip-link: mention bridge port's default mcast_flood state
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=609b90aa3fb1
- [iproute2-next,v3,7/7] man: ip-link: whitespace fixes to odd line breaks mid sentence
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=2dee2101f6e9
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:[~2022-03-12 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:23 [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 1/7] bridge: support for controlling flooding of broadcast " Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 2/7] man: bridge: document new bcast_flood flag for bridge ports Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 3/7] man: bridge: add missing closing " in bridge show mdb Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 4/7] ip: iplink_bridge_slave: support for broadcast flooding Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 5/7] man: ip-link: document new bcast_flood flag on bridge ports Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 6/7] man: ip-link: mention bridge port's default mcast_flood state Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 7/7] man: ip-link: whitespace fixes to odd line breaks mid sentence Joachim Wiberg
2022-03-10 9:01 ` [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Nikolay Aleksandrov
2022-03-12 16: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=164710141170.15431.13449021992708210326.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.org \
--cc=troglobit@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 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.