mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <UNGLinuxDriver@microchip.com>, <davem@davemloft.net>,
	<kuba@kernel.org>, <linux@armlinux.org.uk>,
	<f.fainelli@gmail.com>, <vivien.didelot@gmail.com>,
	<vladimir.oltean@nxp.com>, <andrew@lunn.ch>,
	Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next 0/3] net: lan966x: add support for mcast snooping
Date: Fri, 4 Feb 2022 10:14:49 +0100	[thread overview]
Message-ID: <20220204091452.403706-1-horatiu.vultur@microchip.com> (raw)

Implement the switchdev callback SWITCHDEV_ATTR_ID_BRIDGE_MC_DISABLED
to allow to enable/disable multicast snooping.

Horatiu Vultur (3):
  net: lan966x: Update the PGID used by IPV6 data frames
  net: lan966x: Implement the callback
    SWITCHDEV_ATTR_ID_BRIDGE_MC_DISABLED
  net: lan966x: Update mdb when enabling/disabling mcast_snooping

 .../ethernet/microchip/lan966x/lan966x_main.c | 41 ++++++++++++-
 .../ethernet/microchip/lan966x/lan966x_main.h |  3 +
 .../ethernet/microchip/lan966x/lan966x_mdb.c  | 45 ++++++++++++++
 .../ethernet/microchip/lan966x/lan966x_regs.h | 18 ++++++
 .../microchip/lan966x/lan966x_switchdev.c     | 61 +++++++++++++++++++
 5 files changed, 166 insertions(+), 2 deletions(-)

-- 
2.33.0


             reply	other threads:[~2022-02-04  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  9:14 Horatiu Vultur [this message]
2022-02-04  9:14 ` [PATCH net-next 1/3] net: lan966x: Update the PGID used by IPV6 data frames Horatiu Vultur
2022-02-04  9:14 ` [PATCH net-next 2/3] net: lan966x: Implement the callback SWITCHDEV_ATTR_ID_BRIDGE_MC_DISABLED Horatiu Vultur
2022-02-04  9:14 ` [PATCH net-next 3/3] net: lan966x: Update mdb when enabling/disabling mcast_snooping Horatiu Vultur
2022-02-05 15:10 ` [PATCH net-next 0/3] net: lan966x: add support for mcast snooping 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=20220204091452.403706-1-horatiu.vultur@microchip.com \
    --to=horatiu.vultur@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®