netdev - Re: [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c

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]

Date:	Mon, 4 Jul 2016 14:40:28 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	andrew@...n.ch, netdev@...r.kernel.org,
	vivien.didelot@...oirfairelinux.com
Subject: Re: [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c

Le 29/06/2016 03:12, David Miller a écrit :
> From: Florian Fainelli <f.fainelli@...il.com>
> Date: Mon, 27 Jun 2016 18:19:28 -0700
> 
>> 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.
> 
> I assume therefore that this series will be resubmitted with an
> accompanying example in-tree conversion.
> 

That is correct, although patches 1-4 could be applied immediately as
they are mostly preparatory steps to patches 5-6, I don't mind resending
this at a later time though (probably for the next net-next merge window
I assume).
-- 
Florian