From: Andrew Lunn <andrew@lunn.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
"Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: Re: [PATCH net-next 5/5 v3] net: gemini: Indicate that we can handle jumboframes
Date: Wed, 11 Jul 2018 21:57:01 +0200 [thread overview]
Message-ID: <20180711195701.GB21430@lunn.ch> (raw)
In-Reply-To: <20180711193245.21980-5-linus.walleij@linaro.org>
On Wed, Jul 11, 2018 at 09:32:45PM +0200, Linus Walleij wrote:
> The hardware supposedly handles frames up to 10236 bytes and
> implements .ndo_change_mtu() so accept 10236 minus the ethernet
> header for a VLAN tagged frame on the netdevices. Use
> ETH_MIN_MTU as minimum MTU.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2018-07-11 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:32 [PATCH net-next 1/5 v3] net: gemini: Look up L3 maxlen from table Linus Walleij
2018-07-11 19:32 ` [PATCH net-next 2/5 v3] net: gemini: Improve connection prints Linus Walleij
2018-07-11 19:57 ` Andrew Lunn
2018-07-13 0:39 ` David Miller
2018-07-11 19:32 ` [PATCH net-next 3/5 v3] net: gemini: Allow multiple ports to instantiate Linus Walleij
2018-07-13 0:39 ` David Miller
2018-07-11 19:32 ` [PATCH net-next 4/5 v3] net: gemini: Move main init to port Linus Walleij
2018-07-13 0:39 ` David Miller
2018-07-11 19:32 ` [PATCH net-next 5/5 v3] net: gemini: Indicate that we can handle jumboframes Linus Walleij
2018-07-11 19:57 ` Andrew Lunn [this message]
2018-07-13 0:39 ` David Miller
2018-07-13 0:39 ` [PATCH net-next 1/5 v3] net: gemini: Look up L3 maxlen from table 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=20180711195701.GB21430@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=ulli.kroll@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.