From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
amcohen@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/5] mlxsw: Handle MTU values
Date: Sat, 15 Jun 2024 02:40:31 +0000 [thread overview]
Message-ID: <171841923124.25457.9944342013124852100.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718275854.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Jun 2024 16:07:53 +0200 you wrote:
> Amit Cohen writes:
>
> The driver uses two values for maximum MTU, but neither is accurate.
> In addition, the value which is configured to hardware is not calculated
> correctly. Handle these issues and expose accurate values for minimum
> and maximum MTU per netdevice.
>
> [...]
Here is the summary with links:
- [net-next,1/5] mlxsw: port: Edit maximum MTU value
https://git.kernel.org/netdev/net-next/c/cae7fd47dfe1
- [net-next,2/5] mlxsw: Adjust MTU value to hardware check
https://git.kernel.org/netdev/net-next/c/d361536fc2df
- [net-next,3/5] mlxsw: spectrum: Set more accurate values for netdevice min/max MTU
https://git.kernel.org/netdev/net-next/c/753aacfc032d
- [net-next,4/5] mlxsw: Use the same maximum MTU value throughout the driver
https://git.kernel.org/netdev/net-next/c/3e7856545d36
- [net-next,5/5] selftests: forwarding: Add test for minimum and maximum MTU
https://git.kernel.org/netdev/net-next/c/4be3dcc9bf04
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-15 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 14:07 [PATCH net-next 0/5] mlxsw: Handle MTU values Petr Machata
2024-06-13 14:07 ` [PATCH net-next 1/5] mlxsw: port: Edit maximum MTU value Petr Machata
2024-06-13 14:07 ` [PATCH net-next 2/5] mlxsw: Adjust MTU value to hardware check Petr Machata
2024-06-13 14:07 ` [PATCH net-next 3/5] mlxsw: spectrum: Set more accurate values for netdevice min/max MTU Petr Machata
2024-06-13 14:07 ` [PATCH net-next 4/5] mlxsw: Use the same maximum MTU value throughout the driver Petr Machata
2024-06-13 14:07 ` [PATCH net-next 5/5] selftests: forwarding: Add test for minimum and maximum MTU Petr Machata
2024-06-15 2:40 ` 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=171841923124.25457.9944342013124852100.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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).