public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>
Subject: Re: [PATCH net-next v3 0/3] net: lan966x: Extend switchdev with mdb support
Date: Tue, 4 Jan 2022 17:22:11 +0000	[thread overview]
Message-ID: <20220104172210.hz75ymy2uweing5s@skbuf> (raw)
In-Reply-To: <20220104153338.425250-1-horatiu.vultur@microchip.com>

On Tue, Jan 04, 2022 at 04:33:35PM +0100, Horatiu Vultur wrote:
> This patch series extends lan966x with mdb support by implementing
> the switchdev callbacks: SWITCHDEV_OBJ_ID_PORT_MDB and
> SWITCHDEV_OBJ_ID_HOST_MDB.
> It adds support for both ipv4/ipv6 entries and l2 entries.
> 
> v2->v3:
> - rename PGID_FIRST and PGID_LAST to PGID_GP_START and PGID_GP_END
> - don't forget and relearn an entry for the CPU if there are more
>   references to the cpu.
> 
> v1->v2:
> - rename lan966x_mac_learn_impl to __lan966x_mac_learn
> - rename lan966x_mac_cpu_copy to lan966x_mac_ip_learn
> - fix grammar and typos in comments and commit messages
> - add reference counter for entries that copy frames to CPU
> 
> Horatiu Vultur (3):
>   net: lan966x: Add function lan966x_mac_ip_learn()
>   net: lan966x: Add PGID_GP_START and PGID_GP_END
>   net: lan966x: Extend switchdev with mdb support
> 
>  .../net/ethernet/microchip/lan966x/Makefile   |   2 +-
>  .../ethernet/microchip/lan966x/lan966x_mac.c  |  36 +-
>  .../ethernet/microchip/lan966x/lan966x_main.c |   2 +
>  .../ethernet/microchip/lan966x/lan966x_main.h |  26 +-
>  .../ethernet/microchip/lan966x/lan966x_mdb.c  | 506 ++++++++++++++++++
>  .../ethernet/microchip/lan966x/lan966x_regs.h |   6 +
>  .../microchip/lan966x/lan966x_switchdev.c     |   8 +
>  .../ethernet/microchip/lan966x/lan966x_vlan.c |   7 +-
>  8 files changed, 584 insertions(+), 9 deletions(-)
>  create mode 100644 drivers/net/ethernet/microchip/lan966x/lan966x_mdb.c
> 
> -- 
> 2.33.0
>

For the series:

Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>

  parent reply	other threads:[~2022-01-04 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 15:33 [PATCH net-next v3 0/3] net: lan966x: Extend switchdev with mdb support Horatiu Vultur
2022-01-04 15:33 ` [PATCH net-next v3 1/3] net: lan966x: Add function lan966x_mac_ip_learn() Horatiu Vultur
2022-01-04 15:33 ` [PATCH net-next v3 2/3] net: lan966x: Add PGID_GP_START and PGID_GP_END Horatiu Vultur
2022-01-04 15:33 ` [PATCH net-next v3 3/3] net: lan966x: Extend switchdev with mdb support Horatiu Vultur
2022-01-04 17:22 ` Vladimir Oltean [this message]
2022-01-05 11:30 ` [PATCH net-next v3 0/3] " 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=20220104172210.hz75ymy2uweing5s@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox