Received-SPF: pass (google.com: domain of linux-kernel+bounces-215829-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Paul Barker <paul.barker.ct@bp.renesas.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	=?UTF-8?q?Niklas=20S=C3=B6derlund?= <niklas.soderlund+renesas@ragnatech.se>
Cc: Paul Barker <paul.barker.ct@bp.renesas.com>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Mitsuhiro Kimura <mitsuhiro.kimura.kc@renesas.com>,
	netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [net-next PATCH 0/2] Fix maximum TX/RX frame sizes in ravb driver
Date: Sat, 15 Jun 2024 11:30:36 +0100
Message-Id: <20240615103038.973-1-paul.barker.ct@bp.renesas.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

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
-- 
2.39.2