linux-kernel - Re: [PATCH net-next v2] net: dsa: b53: Do not force CPU to be always tagged

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <162327240400.12172.12511880467816959107.git-patchwork-notify@kernel.org>
Date:   Wed, 09 Jun 2021 21:00:04 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     netdev@...r.kernel.org, mnhagan88@...il.com, andrew@...n.ch,
        vivien.didelot@...il.com, olteanv@...il.com, davem@...emloft.net,
        kuba@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: b53: Do not force CPU to be always
 tagged

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue,  8 Jun 2021 14:22:04 -0700 you wrote:
> Commit ca8931948344 ("net: dsa: b53: Keep CPU port as tagged in all
> VLANs") forced the CPU port to be always tagged in any VLAN membership.
> This was necessary back then because we did not support Broadcom tags
> for all configurations so the only way to differentiate tagged and
> untagged traffic while DSA_TAG_PROTO_NONE was used was to force the CPU
> port into being always tagged.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: dsa: b53: Do not force CPU to be always tagged
    https://git.kernel.org/netdev/net-next/c/2c32a3d3c233

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html