netdev - Re: [patch net-next 00/18] mlxsw: Improve extensibility

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20170526.152139.1067635701572902907.davem@davemloft.net>
Date:   Fri, 26 May 2017 15:21:39 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     jiri@...nulli.us
Cc:     netdev@...r.kernel.org, idosch@...lanox.com, mlxsw@...lanox.com,
        stephen@...workplumber.org, nikolay@...ulusnetworks.com
Subject: Re: [patch net-next 00/18] mlxsw: Improve extensibility

From: David Miller <davem@...emloft.net>
Date: Fri, 26 May 2017 15:20:35 -0400 (EDT)

> Nice cleanups and consolidation, but like Nikolay I'm not so sure
> about all the exports.
> 
> It might even be cleaner (believe it or not) to have the bridge
> structure (or at least a subset of it) be something public that
> drivers can query using inline helpers.

Just to be clear I did apply this series, and the above is about
future considerations.

Thanks.