netdev - Re: [PATCH net-next 00/16] mlxsw: Make port split code more generic

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: <20191031.105513.442982327274718870.davem@davemloft.net>
Date:   Thu, 31 Oct 2019 10:55:13 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...sch.org
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, mlxsw@...lanox.com,
        idosch@...lanox.com
Subject: Re: [PATCH net-next 00/16] mlxsw: Make port split code more generic

From: Ido Schimmel <idosch@...sch.org>
Date: Thu, 31 Oct 2019 11:42:05 +0200

> From: Ido Schimmel <idosch@...lanox.com>
> 
> Jiri says:
> 
> Currently, we assume some limitations and constant values which are not
> applicable for Spectrum-3 which has 8 lanes ports (instead of previous 4
> lanes).
> 
> This patch does 2 things:
> 
> 1) Generalizes the code to not use constants so it can work for 4, 8 and
>    possibly 16 lanes.
> 
> 2) Enforces some assumptions we had in the code but did not check.

Series looks good, applied to net-next.

Thanks.