netdev - Re: [PATCH 0/7] dsa: marvell: Add support for mv88e6071 and 6020 switches

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]

Date:   Mon, 3 Apr 2023 14:55:26 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     Lukasz Majewski <lukma@...x.de>
Cc:     Andrew Lunn <andrew@...n.ch>, Russell King <linux@...linux.org.uk>,
        Eric Dumazet <edumazet@...gle.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Alexander Duyck <alexander.duyck@...il.com>,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] dsa: marvell: Add support for mv88e6071 and 6020
 switches

Hello Lukasz,

On Thu, Mar 09, 2023 at 01:54:14PM +0100, Lukasz Majewski wrote:
> This patch set provides following changes:
> 
> - Provide support for mv88e6020 and mv88e6071 switch circuits (the
>   "Link Street" family of products including added earlier to this
>   driver mv88e6250 and mv88e6220).
> 
> - Add the max_frame size variable to specify the buffer size for the
>   maximal frame size
> 
> - The above change required adjusting all supported devices in the
>   mv88e6xxx driver, as the current value assignment is depending
>   on the set of provided callbacks for each switch circuit - i.e.
>   until now the value was not explicitly specified.
> 
> - As the driver for Marvell's mv88e6xxx switches was rather complicated
>   the intermediate function (removed by the end of this patch set)
>   has been introduced. It was supposed to both validate the provided
>   values deduced from the code and leave a trace of the exact
>   methodology used.

The problem with MTU 1492 has been resolved as commit 7e9517375a14
("net: dsa: mv88e6xxx: fix max_mtu of 1492 on 6165, 6191, 6220, 6250,
6290"), is present in net-next, and as such, you are free to resubmit
this patchset on top of the current net-next.gi/main whenever you feel
like it, no need to wait for a merge window.