From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>,
Chris Healy <cphealy@gmail.com>,
Fugang Duan <fugang.duan@nxp.com>
Subject: Re: [PATCH net-next 0/2] Fix MTU warnings for fec/mv886xxx combo
Date: Sat, 11 Jul 2020 22:26:18 +0100 [thread overview]
Message-ID: <20200711212618.GP1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200711203206.1110108-1-andrew@lunn.ch>
On Sat, Jul 11, 2020 at 10:32:04PM +0200, Andrew Lunn wrote:
> Since changing the MTU of dsa slave interfaces was implemented, the
> fec/mv88e6xxx combo has been giving warnings:
>
> [ 2.275925] mv88e6085 0.2:00: nonfatal error -95 setting MTU on port 9
> [ 2.284306] eth1: mtu greater than device maximum
> [ 2.287759] fec 400d1000.ethernet eth1: error -22 setting MTU to include DSA overhead
>
> This patchset adds support for changing the MTU on mv88e6xxx switches,
> which do support jumbo frames. And it modifies the FEC driver to
> support its true MTU range, which is larger than the default Ethernet
> MTU.
It's not just the fec/mv88e6xxx combo - I've been getting them on
Clearfog too. It just hasn't been important enough to report yet.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-11 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 20:32 [PATCH net-next 0/2] Fix MTU warnings for fec/mv886xxx combo Andrew Lunn
2020-07-11 20:32 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: Implement MTU change Andrew Lunn
2020-07-11 23:29 ` Marek Behun
2020-07-11 23:52 ` Andrew Lunn
2020-07-11 20:32 ` [PATCH net-next 2/2] net: fec: Set max MTU size to allow the MTU to be changed Andrew Lunn
2020-07-11 21:26 ` Russell King - ARM Linux admin [this message]
2020-07-11 22:48 ` [PATCH net-next 0/2] Fix MTU warnings for fec/mv886xxx combo Andrew Lunn
2020-07-12 22:23 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200711212618.GP1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).