From: Vladimir Oltean <olteanv@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sergei Antonov <saproj@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH v4 net-next] net: ftmac100: support mtu > 1500
Date: Mon, 24 Oct 2022 19:24:36 +0300 [thread overview]
Message-ID: <20221024162436.y22ynsugtguyeteh@skbuf> (raw)
In-Reply-To: <20221024162145.4t35ucrwpafbyhbc@skbuf>
On Mon, Oct 24, 2022 at 07:21:45PM +0300, Vladimir Oltean wrote:
> The only given guarantee is that packets with an L2 length <= dev->mtu
> are accepted.
L2 payload* length, i.e. the bytes between the Ethernet/VLAN header and
the FCS.
prev parent reply other threads:[~2022-10-24 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 16:20 [PATCH v4 net-next] net: ftmac100: support mtu > 1500 Sergei Antonov
2022-10-19 16:25 ` Sergei Antonov
2022-10-19 16:55 ` Vladimir Oltean
2022-10-19 18:36 ` Sergei Antonov
2022-10-19 18:42 ` Vladimir Oltean
2022-10-24 15:50 ` Sergei Antonov
2022-10-24 16:09 ` Andrew Lunn
2022-10-24 16:21 ` Vladimir Oltean
2022-10-24 16:24 ` Vladimir Oltean [this message]
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=20221024162436.y22ynsugtguyeteh@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saproj@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).