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
| ||
|
Date: Mon, 27 Jun 2016 18:19:28 -0700 From: Florian Fainelli <f.fainelli@...il.com> To: Andrew Lunn <andrew@...n.ch> Cc: netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>, Vivien Didelot <vivien.didelot@...oirfairelinux.com> Subject: Re: [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c 2016-06-27 18:05 GMT-07:00 Andrew Lunn <andrew@...n.ch>: > On Mon, Jun 27, 2016 at 05:52:37PM -0700, Florian Fainelli wrote: >> Hi all, >> >> This patch series adds support for platform data using the new code from >> net/dsa/dsa2.c. The motivation behind this is that we have a bit of in tree >> platforms (ar7, bcm47xx, x86, others) that could be benefiting from the new >> dsa_register_switch() API model but do not support Device Tree, nor is there a >> plan to bring Device Tree to these platforms (time vs. benefits). > > Hi Florian > > Please could you convert an in tree device to actually use this. Sure, I don't think there are going to be in tree users who need the dsa2_port_link information most of what we have is typically single chip, and so in that case, we can even re-use the existing dsa_platform_data. -- Florian
Powered by blists - more mailing lists