From: Jakub Kicinski <kuba@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Sayantan Nandy <sayantann11@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
sayantan.nandy@airoha.com, bread.hsu@airoha.com,
kuldeep.malik@airoha.com, aniket.negi@airoha.com,
rajeev.kumar@airoha.com
Subject: Re: [PATCH] net: airoha_eth: increase max mtu to 9220 for DSA jumbo frames
Date: Thu, 15 Jan 2026 19:05:46 -0800 [thread overview]
Message-ID: <20260115190546.5ede6750@kernel.org> (raw)
In-Reply-To: <aWjuM3Ov0e45QyW4@lore-desk>
On Thu, 15 Jan 2026 14:40:03 +0100 Lorenzo Bianconi wrote:
> > The Industry standard for jumbo frame MTU is 9216 bytes. When using DSA
> > sub-system, an extra 4 byte tag is added to each frame. To allow users
> > to set the standard 9216-byte MTU via ifconfig,increase AIROHA_MAX_MTU
> > to 9220 bytes (9216+4).
> >
> > Signed-off-by: Sayantan Nandy <sayantann11@gmail.com>
>
> I think the patch is fine, but here you are missing to specify this is v2
> and this patch targets net-next. Moreover, please wait 24h before reposting
> a new version of the same patch.
FWIW this is a good reminder for Sayantan for the future but it doesn't
merit a repost in itself. net-next is our default tree, and pw bot
guessed correctly.
That said I think Andrews request warrants some extra testing here so:
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-16 3:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:48 [PATCH] net: airoha_eth: increase max mtu to 9220 for DSA jumbo frames Sayantan Nandy
2026-01-15 9:39 ` Benjamin Larsson
2026-01-15 13:40 ` Lorenzo Bianconi
2026-01-16 3:05 ` Jakub Kicinski [this message]
2026-01-15 17:41 ` Andrew Lunn
2026-01-15 19:10 ` Benjamin Larsson
2026-01-16 1:08 ` Andrew Lunn
2026-01-16 10:48 ` Benjamin Larsson
2026-01-16 14:21 ` Andrew Lunn
[not found] ` <CADJVu8XP_wBudwOrT1OLhcZ3-9Qoci8FQzw+yyxnogiC2Asx5w@mail.gmail.com>
2026-01-16 14:56 ` Andrew Lunn
2026-01-16 15:05 ` Benjamin Larsson
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=20260115190546.5ede6750@kernel.org \
--to=kuba@kernel.org \
--cc=aniket.negi@airoha.com \
--cc=bread.hsu@airoha.com \
--cc=kuldeep.malik@airoha.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rajeev.kumar@airoha.com \
--cc=sayantan.nandy@airoha.com \
--cc=sayantann11@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 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.