mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yunpeng Tian <shionthanatos@gmail.com>
Cc: tung.quang.nguyen@est.tech, jmaloy@redhat.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, gmwgg05@gmail.com, npczmd@qq.com,
	xiao-yu.zhou@connect.polyu.hk, jupmouse@gmail.com
Subject: Re: [PATCH net] tipc: bound the device MTU accepted for L2 bearers
Date: Thu, 08 Oct 2026 00:20:07 +0000	[thread overview]
Message-ID: <179141880727.3746804.9812166172922423537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261003035018.397-1-shionthanatos@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  2 Oct 2026 20:50:18 -0700 you wrote:
> struct tipc_bearer keeps the bearer MTU in a u32 while struct tipc_link
> keeps the link MTU in a u16.  tipc_enable_l2_media() and the
> NETDEV_CHANGEMTU notifier both do b->mtu = dev->mtu, tipc_link_create()
> assigns that into l->mtu, and tipc_link_set_queue_limits() divides by it:
> 
> 	int max_bulk = TIPC_MAX_PUBL / (l->mtu / ITEM_SIZE);
> 
> [...]

Here is the summary with links:
  - [net] tipc: bound the device MTU accepted for L2 bearers
    https://git.kernel.org/netdev/net-next/c/592d0fdb02df

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03  3:50 Yunpeng Tian
2026-10-03  3:54 ` netdev-bot+sinfo
2026-10-05 10:12 ` Tung Quang Nguyen
2026-10-08  0:20 ` patchwork-bot+netdevbpf [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=179141880727.3746804.9812166172922423537.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gmwgg05@gmail.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=jupmouse@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=npczmd@qq.com \
    --cc=pabeni@redhat.com \
    --cc=shionthanatos@gmail.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    --cc=xiao-yu.zhou@connect.polyu.hk \
    /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
all inboxes | Powered by JetHome®