netdev - Re: [PATCH net-next-v2 0/6] net: dsa: Make bcm_sf2 utilize b53

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] [day] [month] [year] [list]

Message-Id: <20160826.120830.1882445675319317827.davem@davemloft.net>
Date:   Fri, 26 Aug 2016 12:08:30 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     f.fainelli@...il.com
Cc:     netdev@...r.kernel.org, jonas.gorski@...il.com, andrew@...n.ch,
        vivien.didelot@...oirfairelinux.com
Subject: Re: [PATCH net-next-v2 0/6] net: dsa: Make bcm_sf2 utilize
 b53_common

From: Florian Fainelli <f.fainelli@...il.com>
Date: Thu, 25 Aug 2016 09:24:35 -0700

> Hi all,
> 
> This patch series makes the bcm_sf2 driver utilize a large number of the core
> functions offered by the b53_common driver since the SWITCH_CORE registers are
> mostly register compatible with the switches driven by b53_common.
> 
> In order to accomplish that, we just override the dsa_driver_ops callbacks that
> we need to. There are still integration specific logic from the bcm_sf2 that we
> cannot absorb into b53_common because it is just not there, mostly in the area
> of link management and power management, but most of the features are within
> b53_common now: VLAN, FDB, bridge
> 
> Along the process, we also improve support for the BCM58xx SoCs, since those
> also have the same version of the switching IP that 7445 has (for which bcm_sf2
> was developed).
> 
> Changes in v2:
> 
> - rebased against "net: dsa: rename switch operations structure"

This still doesn't apply cleanly to net-next, can you respin it one more
time and double check your work?

Thanks.