[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2131a94-ab79-64ee-20d2-e977b082f83c@omp.ru>
Date: Mon, 17 Jun 2024 22:45:52 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Paul Barker <paul.barker.ct@...renesas.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
CC: Biju Das <biju.das.jz@...renesas.com>, Claudiu Beznea
<claudiu.beznea.uj@...renesas.com>, Lad Prabhakar
<prabhakar.mahadev-lad.rj@...renesas.com>, Mitsuhiro Kimura
<mitsuhiro.kimura.kc@...esas.com>, <netdev@...r.kernel.org>,
<linux-renesas-soc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [net-next PATCH 1/2] net: ravb: Fix maximum MTU for GbEth devices
On 6/17/24 10:38 PM, Sergey Shtylyov wrote:
[...]
>> The datasheets for all SoCs using the GbEth IP specify a maximum
>> transmission frame size of 1.5 kByte. I've confirmed through internal
>> discussions that support for 1522 byte frames has been validated, which
>> allows us to support the default MTU of 1500 bytes after reserving space
>> for the Ethernet header, frame checksums and an optional VLAN tag.
>>
>> Fixes: 2e95e08ac009 ("ravb: Add rx_max_buf_size to struct ravb_hw_info")
>> Signed-off-by: Paul Barker <paul.barker.ct@...renesas.com>
> [...]
>
> Reviewed-by: Sergey Shtylyov <s.shtylyov@....ru>
Sounds like this is a also fix for the net.git tho?
[...]
MBR, Sergey
Powered by blists - more mailing lists