Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
	stephen@networkplumber.org, petrm@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH iproute2-next 2/2] bridge: vlan: Add support for neigh_forward_grat
Date: Wed, 20 May 2026 13:46:06 +0300	[thread overview]
Message-ID: <ag2Q7oW6EE1vTRhX@penguin> (raw)
In-Reply-To: <ag2M3moiivqEvfNG@penguin>

On Wed, May 20, 2026 at 01:28:46PM +0300, Nikolay Aleksandrov wrote:
> On Sun, May 17, 2026 at 11:25:01AM +0300, Danielle Ratson wrote:
> > Add support for controlling gratuitous ARP and unsolicited NA
> > forwarding at the per-VLAN level via the neigh_forward_grat option.
> > 
> > This allows configuring the option via:
> > $ bridge vlan set dev <port> vid <vlan> neigh_forward_grat {on|off}
> > 
> > Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> > Reviewed-by: Petr Machata <petrm@nvidia.com>
> > Signed-off-by: Danielle Ratson <danieller@nvidia.com>
> > ---
> >  bridge/vlan.c     | 18 ++++++++++++++++++
> >  man/man8/bridge.8 | 15 ++++++++++++++-
> >  2 files changed, 32 insertions(+), 1 deletion(-)
> > 
>  
> Acked-by: Nikolay Aleksandrov <razor@blackwall.org>

sorry for the noise, for some reason I saw these marked as
new without any replies in mutt and reviewed them again. :)

  reply	other threads:[~2026-05-20 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  8:24 [PATCH iproute2-next 0/2] Add support for neigh_forward_grat Danielle Ratson
2026-05-17  8:25 ` [PATCH iproute2-next 1/2] iplink: bridge_slave: " Danielle Ratson
2026-05-17 14:09   ` Nikolay Aleksandrov
2026-05-20 10:28   ` Nikolay Aleksandrov
2026-05-17  8:25 ` [PATCH iproute2-next 2/2] bridge: vlan: " Danielle Ratson
2026-05-17 14:10   ` Nikolay Aleksandrov
2026-05-20 10:28   ` Nikolay Aleksandrov
2026-05-20 10:46     ` Nikolay Aleksandrov [this message]
2026-05-20  0:50 ` [PATCH iproute2-next 0/2] " 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=ag2Q7oW6EE1vTRhX@penguin \
    --to=razor@blackwall.org \
    --cc=danieller@nvidia.com \
    --cc=dsahern@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@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