[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3cad5dd7-2663-d0e4-14ba-b62814c6814e@omp.ru>
Date: Sun, 16 Jun 2024 22:22:43 +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 0/2] Fix maximum TX/RX frame sizes in ravb driver
On 6/15/24 1:30 PM, Paul Barker wrote:
> These patches fix a couple of bugs in the maximum supported TX/RX frame sizes
> in the ravb driver.
>
> * For the GbEth IP, we were advertising a maximum TX frame size/MTU that was
> larger that the maximum the hardware can transmit.
>
> * For the R-Car AVB IP, we were unnecessarily setting the maximum RX frame
> size/MRU based on the MTU, which by default is smaller than the maximum the
> hardware can receive.
>
> Paul Barker (2):
> net: ravb: Fix maximum MTU for GbEth devices
> net: ravb: Set R-Car RX frame size limit correctly
>
> drivers/net/ethernet/renesas/ravb.h | 1 +
> drivers/net/ethernet/renesas/ravb_main.c | 10 ++++++++--
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
>
> base-commit: 934c29999b57b835d65442da6f741d5e27f3b584
>
DaveM & Co, I'm planning to review these patches on Monday evening...
MBR, Sergey
Powered by blists - more mailing lists