From: Arnd Bergmann <arnd@arndb.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sasha Levin <sashal@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>, Joel Stanley <joel@jms.id.au>,
David Wilder <wilder@us.ibm.com>,
Dylan Hung <dylan_hung@aspeedtech.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
guoheyi@linux.alibaba.com, chenhao288@hisilicon.com,
Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH AUTOSEL 5.17 10/12] net: ftgmac100: Disable hardware checksum on AST2600
Date: Tue, 24 May 2022 20:47:51 +0200 [thread overview]
Message-ID: <CAK8P3a2EZKnLB5c9YuKbaug16tG7juidmQ+g-wLNHx_-zxTD5A@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3J6gh-0Z8JKEBDva7ox39ps5CCxJ4K7T1LyWMbTHna8Q@mail.gmail.com>
On Tue, May 24, 2022 at 8:47 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Tue, May 24, 2022 at 5:59 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > # ip link set mtu 1410 dev eth0
> >
> > The observed results:
> >
> > 1500 - good
> > 1434 - bad
> > 1400 - good
> > 1410 - bad
> > 1420 - good
>
> Does it require multiples of four? Maybe it just skips the last bytes?
Nevermind, I missed that this was a backport of a merged patch, rather
than a new one.
Arnd
next prev parent reply other threads:[~2022-05-24 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220524155929.826793-1-sashal@kernel.org>
2022-05-24 15:59 ` [PATCH AUTOSEL 5.17 08/12] net: af_key: check encryption module availability consistency Sasha Levin
2022-05-24 18:09 ` Jakub Kicinski
2022-05-25 5:20 ` Jakub Kicinski
2022-05-24 15:59 ` [PATCH AUTOSEL 5.17 09/12] nfc: pn533: Fix buggy cleanup order Sasha Levin
2022-05-24 15:59 ` [PATCH AUTOSEL 5.17 10/12] net: ftgmac100: Disable hardware checksum on AST2600 Sasha Levin
2022-05-24 18:47 ` Arnd Bergmann
2022-05-24 18:47 ` Arnd Bergmann [this message]
2022-05-24 19:01 ` Jakub Kicinski
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=CAK8P3a2EZKnLB5c9YuKbaug16tG7juidmQ+g-wLNHx_-zxTD5A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=dylan_hung@aspeedtech.com \
--cc=edumazet@google.com \
--cc=guoheyi@linux.alibaba.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wilder@us.ibm.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).