From: Stijn Cleynhens <stijncleynhens@gmail.com>
To: "Alvin Šipraga" <alvin.sipraga@analog.com>
Cc: netdev@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Mieczyslaw Nalewaj <namiltd@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/2] net: dsa: realtek: rtl8365mb: use IVL in VLAN 0
Date: Fri, 6 Nov 2026 16:01:24 +0100 [thread overview]
Message-ID: <20261106150124.3630781-1-stijncleynhens@gmail.com> (raw)
In-Reply-To: <autLlP81HFeMyICc@analog.com>
On Wed, Nov 04, 2026 at 04:22:58PM +0100, Alvin Šipraga wrote:
> Yes, all this makes sense. I actually remember doing basically the same
> thing back when I was working on this, but it seems not to have survived
> the final work by Luiz. It would be good to get his input on why.
Luiz, do you remember a reason the IVL setup of VID 0 was dropped? I
could not find one, and the switch only matches the driver's VID 0
entries with it.
> So I'm not sure I like this function being added to the vlan.c
> library. Semantically it makes more sense to me for the main.c driver to
> actually call rtl8365mb_vlan4k_port_add() for each port, so as to
> explicitly say: "all ports are, one way or another, members of this
> neutral VLAN". Then you would get IVL automatically.
I kept it out of rtl8365mb_vlan_4k_port_add() on purpose: making every
port a member of VID 0 also sets the member mask, which the ingress
filter of a VLAN-aware port then checks. I only wanted to change the
learning mode, not which frames a filtering port accepts.
> Reviewed-by: Alvin Šipraga <alvin.sipraga@analog.com>
Thanks!
Stijn
next prev parent reply other threads:[~2026-11-06 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:25 [PATCH net 0/2] net: dsa: realtek: rtl8365mb: fix FDB lookups in VLAN-unaware bridges Stijn Cleynhens
2026-11-04 8:25 ` [PATCH net 1/2] net: dsa: realtek: rtl8365mb: use IVL in VLAN 0 Stijn Cleynhens
2026-11-04 15:22 ` Alvin Šipraga
2026-11-06 15:01 ` Stijn Cleynhens [this message]
2026-11-04 8:25 ` [PATCH net 2/2] net: dsa: realtek: rtl8365mb: keep the neutral PVID in VLAN-unaware bridges Stijn Cleynhens
2026-11-04 15:57 ` Alvin Šipraga
2026-11-06 15:02 ` Stijn Cleynhens
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=20261106150124.3630781-1-stijncleynhens@gmail.com \
--to=stijncleynhens@gmail.com \
--cc=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=namiltd@yahoo.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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®