netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org,
	razor@blackwall.org, liuhangbin@gmail.com,
	Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH iproute2-next 0/2] bridge: Add support for per-{Port, VLAN} neighbor suppression
Date: Mon, 24 Apr 2023 19:09:49 +0300	[thread overview]
Message-ID: <20230424160951.232878-1-idosch@nvidia.com> (raw)

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".

Ido Schimmel (2):
  bridge: vlan: Add support for neigh_suppress option
  bridge: link: Add support for neigh_vlan_suppress option

 bridge/link.c            | 19 +++++++++++++++++++
 bridge/vlan.c            | 18 ++++++++++++++++++
 ip/iplink_bridge_slave.c | 10 ++++++++++
 man/man8/bridge.8        | 19 ++++++++++++++++++-
 man/man8/ip-link.8.in    |  8 ++++++++
 5 files changed, 73 insertions(+), 1 deletion(-)

-- 
2.40.0


             reply	other threads:[~2023-04-24 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 16:09 Ido Schimmel [this message]
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 ` [PATCH iproute2-next 0/2] bridge: Add support for per-{Port, VLAN} neighbor suppression patchwork-bot+netdevbpf

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=20230424160951.232878-1-idosch@nvidia.com \
    --to=idosch@nvidia.com \
    --cc=dsahern@gmail.com \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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 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).