public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Sayantan Nandy <sayantann11@gmail.com>, lorenzo@kernel.org
Cc: 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
Subject: Re: [PATCH] net: airoha_eth: increase max MTU to 9220 for DSA jumbo frame support 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).
Date: Tue, 20 Jan 2026 11:08:39 +0100	[thread overview]
Message-ID: <f35ba439-bb32-4c62-a057-29f45f95083e@redhat.com> (raw)
In-Reply-To: <20260115064043.45589-1-sayantann11@gmail.com>

On 1/15/26 7:40 AM, Sayantan Nandy wrote:
> This change ensures compatibility with common network equipment and jumbo frame configurations.

It looks like that a significant amount of the description landed in the
subject, which is not good.

Please reformat the changelog carefully.

Also it looks like this is intended to address a bug; if so it should
target the 'net' tree and include a Fixes tag.

Thanks,

Paolo


      parent reply	other threads:[~2026-01-20 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  6:40 [PATCH] net: airoha_eth: increase max MTU to 9220 for DSA jumbo frame support 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) Sayantan Nandy
2026-01-15  7:57 ` Lorenzo Bianconi
2026-01-20 10:08 ` Paolo Abeni [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=f35ba439-bb32-4c62-a057-29f45f95083e@redhat.com \
    --to=pabeni@redhat.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox