public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hans Schultz <schultz.hans@gmail•com>
To: Vladimir Oltean <vladimir.oltean@nxp•com>,
	Hans Schultz <schultz.hans@gmail•com>
Cc: "Andrew Lunn" <andrew@lunn•ch>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	"Jakub Kicinski" <kuba@kernel•org>,
	"David S. Miller" <davem@davemloft•net>,
	"Florian Fainelli" <f.fainelli@gmail•com>,
	"Vivien Didelot" <vivien.didelot@gmail•com>,
	"Vladimir Oltean" <olteanv@gmail•com>,
	"Kurt Kanzenbach" <kurt@linutronix•de>,
	"Hauke Mehrtens" <hauke@hauke-m•de>,
	"Woojung Huh" <woojung.huh@microchip•com>,
	"UNGLinuxDriver@microchip•com" <UNGLinuxDriver@microchip•com>,
	"Sean Wang" <sean.wang@mediatek•com>,
	"Landen Chao" <Landen.Chao@mediatek•com>,
	"DENG Qingfang" <dqfext@gmail•com>,
	"Claudiu Manoil" <claudiu.manoil@nxp•com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin•com>,
	"Linus Walleij" <linus.walleij@linaro•org>,
	"Alvin Šipraga" <alsi@bang-olufsen•dk>,
	"George McCollister" <george.mccollister@gmail•com>
Subject: Re: [PATCH v2 net-next 07/10] net: dsa: request drivers to perform FDB isolation
Date: Wed, 27 Apr 2022 13:06:32 +0200	[thread overview]
Message-ID: <86zgk6eqfb.fsf@gmail.com> (raw)
In-Reply-To: <20220427103209.luyfereepqaha7dw@skbuf>

On ons, apr 27, 2022 at 10:32, Vladimir Oltean <vladimir.oltean@nxp•com> wrote:
> On Wed, Apr 27, 2022 at 10:38:18AM +0200, Hans Schultz wrote:
>> 
>> I see that there is definitions for 64bit mac addresses out there, which
>> might also be needed to be supported at some point?
>
> I don't know about 64-bit MAC addresses, do you have more information?
>

I have only seen that there is a section about it in rfc7043:
https://www.rfc-editor.org/rfc/rfc7043

and some in rfc7042 also.

  reply	other threads:[~2022-04-27 11:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  9:22 [PATCH v2 net-next 00/10] DSA FDB isolation Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 01/10] net: dsa: tag_8021q: replace the SVL bridging with VLAN-unaware IVL bridging Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 02/10] net: dsa: tag_8021q: add support for imprecise RX based on the VBID Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 03/10] docs: net: dsa: sja1105: document limitations of tc-flower rule VLAN awareness Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 04/10] net: dsa: felix: delete workarounds present due to SVL tag_8021q bridging Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 05/10] net: dsa: tag_8021q: merge RX and TX VLANs Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 06/10] net: dsa: tag_8021q: rename dsa_8021q_bridge_tx_fwd_offload_vid Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 07/10] net: dsa: request drivers to perform FDB isolation Vladimir Oltean
2022-04-26 15:01   ` Hans Schultz
2022-04-26 16:14     ` Andrew Lunn
2022-04-26 23:17       ` Vladimir Oltean
2022-04-27  8:38         ` Hans Schultz
2022-04-27 10:32           ` Vladimir Oltean
2022-04-27 11:06             ` Hans Schultz [this message]
2022-04-27  6:45       ` Hans Schultz
2022-02-25  9:22 ` [PATCH v2 net-next 08/10] net: dsa: pass extack to .port_bridge_join driver methods Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 09/10] net: dsa: sja1105: enforce FDB isolation Vladimir Oltean
2022-02-25  9:22 ` [PATCH v2 net-next 10/10] net: mscc: ocelot: enforce FDB isolation when VLAN-unaware Vladimir Oltean
2022-02-27 11:10 ` [PATCH v2 net-next 00/10] DSA FDB isolation 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=86zgk6eqfb.fsf@gmail.com \
    --to=schultz.hans@gmail$(echo .)com \
    --cc=Landen.Chao@mediatek$(echo .)com \
    --cc=UNGLinuxDriver@microchip$(echo .)com \
    --cc=alexandre.belloni@bootlin$(echo .)com \
    --cc=alsi@bang-olufsen$(echo .)dk \
    --cc=andrew@lunn$(echo .)ch \
    --cc=claudiu.manoil@nxp$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dqfext@gmail$(echo .)com \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=george.mccollister@gmail$(echo .)com \
    --cc=hauke@hauke-m$(echo .)de \
    --cc=kuba@kernel$(echo .)org \
    --cc=kurt@linutronix$(echo .)de \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=olteanv@gmail$(echo .)com \
    --cc=sean.wang@mediatek$(echo .)com \
    --cc=vivien.didelot@gmail$(echo .)com \
    --cc=vladimir.oltean@nxp$(echo .)com \
    --cc=woojung.huh@microchip$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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