From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, saeedm@nvidia.com, gal@nvidia.com,
leonro@nvidia.com
Subject: Re: [PATCH net-next 0/2] mlx5e update features on config changes
Date: Tue, 29 Oct 2024 19:00:39 +0000 [thread overview]
Message-ID: <173022843923.790671.8221557596485555324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241024164134.299646-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Oct 2024 19:41:31 +0300 you wrote:
> Hi,
>
> This small patchset by Dragos adds a call to netdev_update_features()
> in configuration changes that could impact the features status.
>
> Series generated against:
> commit 81bc949f640f ("selftests: tls: add a selftest for wrapping rec_seq")
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/mlx5e: Update features on MTU change
https://git.kernel.org/netdev/net-next/c/7999da12a670
- [net-next,2/2] net/mlx5e: Update features on ring size change
https://git.kernel.org/netdev/net-next/c/a7b6c074e42d
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-10-29 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 16:41 [PATCH net-next 0/2] mlx5e update features on config changes Tariq Toukan
2024-10-24 16:41 ` [PATCH net-next 1/2] net/mlx5e: Update features on MTU change Tariq Toukan
2024-10-25 8:52 ` Simon Horman
2024-10-24 16:41 ` [PATCH net-next 2/2] net/mlx5e: Update features on ring size change Tariq Toukan
2024-10-25 8:52 ` Simon Horman
2024-10-29 19:00 ` 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=173022843923.790671.8221557596485555324.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 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.