From: patchwork-bot+netdevbpf@kernel.org
To: Tomas Hlavacek <tmshlvck@gmail.com>
Cc: netdev@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
dlan@kernel.org, wangruikang@iscas.ac.cn, stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: spacemit: k1-emac: fix jumbo frame support
Date: Tue, 03 Feb 2026 04:20:05 +0000 [thread overview]
Message-ID: <177009240524.1309272.13521907862288181709.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130102301.477514-1-tmshlvck@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 30 Jan 2026 11:23:01 +0100 you wrote:
> The driver never programs the MAC frame size and jabber registers,
> causing the hardware to reject frames larger than the default 1518
> bytes even when larger DMA buffers are allocated.
>
> Program MAC_MAXIMUM_FRAME_SIZE, MAC_TRANSMIT_JABBER_SIZE, and
> MAC_RECEIVE_JABBER_SIZE based on the configured MTU. Also fix the
> maximum buffer size from 4096 to 4095, since the descriptor buffer
> size field is only 12 bits. Account for double VLAN tags in frame
> size calculations.
>
> [...]
Here is the summary with links:
- [net,v3] net: spacemit: k1-emac: fix jumbo frame support
https://git.kernel.org/netdev/net/c/3125fc170169
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-02-03 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 10:23 [PATCH net v3] net: spacemit: k1-emac: fix jumbo frame support Tomas Hlavacek
2026-02-03 4:20 ` patchwork-bot+netdevbpf [this message]
2026-02-03 9:39 ` [PATCH net v3] net: spacemit: k1-emac: fix jumbo frame support: manual merge Matthieu Baerts
2026-02-03 10:25 ` Vivian Wang
2026-02-03 18:22 ` Tomas Hlavacek
2026-02-20 4:11 ` [PATCH net v3] net: spacemit: k1-emac: fix jumbo frame support patchwork-bot+linux-riscv
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=177009240524.1309272.13521907862288181709.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dlan@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=spacemit@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tmshlvck@gmail.com \
--cc=wangruikang@iscas.ac.cn \
/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