From: Vladimir Oltean <olteanv@gmail.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v4 0/4] net: dsa: ks8995: Post-move fixes
Date: Thu, 26 Mar 2026 12:33:37 +0200 [thread overview]
Message-ID: <20260326103337.wl2zzbmbikg2wvnl@skbuf> (raw)
In-Reply-To: <20260326-ks8995-fixups-v4-0-989abba8f077@kernel.org>
On Thu, Mar 26, 2026 at 10:57:31AM +0100, Linus Walleij wrote:
> Changes in v4:
> - Drop the final "port isolation" (should be better named "port separation")
> patch, due to lack of time to revise the patch. Let's keep this one
> for later.
> - Hope we can merge this first round of fixups so the driver is in some
> reasonable state.
> - Link to v3: https://lore.kernel.org/r/20260219-ks8995-fixups-v3-0-a7fc63fe1916@kernel.org
Hmm, ok...
Andrew, do we have some sort of policy regarding how should DSA_TAG_PROTO_NONE
drivers behave in terms of forwarding? Currently even with this series applied,
this driver doesn't respect the forwarding domains configured using bridges,
even though it marks them as offloaded. But the non-offloading path doesn't
work either, because there is no tagging protocol implemented for software
processing. Not sure at which point we should consider the driver quality
'good enough' for the current release vs the next one.
prev parent reply other threads:[~2026-03-26 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 9:57 [PATCH net v4 0/4] net: dsa: ks8995: Post-move fixes Linus Walleij
2026-03-26 9:57 ` [PATCH net v4 1/4] net: dsa: ks8995: Add shutdown callback Linus Walleij
2026-03-26 10:03 ` Vladimir Oltean
2026-03-26 9:57 ` [PATCH net v4 2/4] net: dsa: microchip: Add fallback Micrel compatibles Linus Walleij
2026-03-26 10:11 ` Vladimir Oltean
2026-03-26 9:57 ` [PATCH net v4 3/4] net: dsa: ks8955: Delete KSZ8864 and KSZ8795 support Linus Walleij
2026-03-26 10:21 ` Vladimir Oltean
2026-03-26 9:57 ` [PATCH net v4 4/4] net: dsa: ks8995: Add stub bridge join/leave Linus Walleij
2026-03-26 10:26 ` Vladimir Oltean
2026-03-26 10:02 ` [PATCH net v4 0/4] net: dsa: ks8995: Post-move fixes Vladimir Oltean
2026-03-26 10:06 ` Vladimir Oltean
2026-03-26 10:33 ` Vladimir Oltean [this message]
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=20260326103337.wl2zzbmbikg2wvnl@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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