[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <060531b4-0561-a5e0-0613-24a2a7b47f09@alliedtelesis.co.nz>
Date: Thu, 23 Jul 2020 20:54:57 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Andrew Lunn <andrew@...n.ch>
CC: "vivien.didelot@...il.com" <vivien.didelot@...il.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] net: dsa: mv88e6xxx: Use chip-wide max frame size for
MTU
On 24/07/20 1:34 am, Andrew Lunn wrote:
> On Thu, Jul 23, 2020 at 03:59:42PM +1200, Chris Packham wrote:
>> Some of the chips in the mv88e6xxx family don't support jumbo
>> configuration per port. But they do have a chip-wide max frame size that
>> can be used. Use this to approximate the behaviour of configuring a port
>> based MTU.
>>
>> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
> Hi Chris
>
> This patch will need a bit of rework for net-next, but the basic idea
> is O.K.
I'll rebase my series on top of net-next.
Powered by blists - more mailing lists