Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: netdev-bot+sashiko@kernel.org, woojung.huh@microchip.com,
	UNGLinuxDriver@microchip.com, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	marex@denx.de, horms@kernel.org, linux@armlinux.org.uk,
	nb@tipi-net.de, netdev@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v15 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling
Date: Fri, 18 Sep 2026 17:48:16 -0700	[thread overview]
Message-ID: <20260918174816.0d77d5dd@kernel.org> (raw)
In-Reply-To: <CAD++jLm7UQGiS9C=HnAUGOmnjA0AvjLc_qOUTRCK0PeRsVn0JA@mail.gmail.com>

On Thu, 17 Sep 2026 23:18:42 +0200 Linus Walleij wrote:
> On Thu, Sep 17, 2026 at 3:22 PM <netdev-bot+sashiko@kernel.org> wrote:
> 
> > Two details worth noting: this only happens with a conduit MAC that strips
> > the non-standard 0x810X TPID into metadata while preserving the port bits,
> > which was not demonstrated here, and the same OUT_BAD outcome already
> > applies to other VLAN-metadata DSA taggers such as the tag_8021q family,
> > where proto becomes ETH_P_XDSA and also has no case in the switch. Should
> > the receive path here rely only on the in-band tag, or is degraded hashing
> > on the conduit acceptable for this configuration?  
> 
> This is just getting too fringe. What about we merge this and look into this
> when we have a user who actually want to do these things on this
> old chip?
> 
> I don't think this is a blocker.

Yes, sorry, I need to modify the emails to call it out more clearly.
We only really care about issues >=Medium severity, but if there are
any such issues found we send out the low ones too just in case.

  reply	other threads:[~2026-09-19  0:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:20 [PATCH net-next v15 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-09-16 10:20 ` [PATCH net-next v15 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-17 13:22   ` netdev-bot+sashiko
2026-09-17 21:15     ` Linus Walleij
2026-09-16 10:20 ` [PATCH net-next v15 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-17 13:22   ` netdev-bot+sashiko
2026-09-17 21:18     ` Linus Walleij
2026-09-19  0:48       ` Jakub Kicinski [this message]
2026-09-16 10:21 ` [PATCH net-next v15 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-17 13:22   ` netdev-bot+sashiko
2026-09-17 21:28     ` Linus Walleij
2026-09-16 10:21 ` [PATCH net-next v15 4/4] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-17 13:22   ` netdev-bot+sashiko
2026-09-17 21:33     ` Linus Walleij
2026-09-19  1:00 ` [PATCH net-next v15 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA 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=20260918174816.0d77d5dd@kernel.org \
    --to=kuba@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marex@denx.de \
    --cc=nb@tipi-net.de \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --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