From: patchwork-bot+netdevbpf@kernel•org
To: Tariq Toukan <tariqt@nvidia•com>
Cc: edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
andrew+netdev@lunn•ch, davem@davemloft•net, saeed@kernel•org,
gal@nvidia•com, leon@kernel•org, saeedm@nvidia•com,
mbloch@nvidia•com, netdev@vger•kernel.org,
linux-rdma@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH net 0/2] mlx5 misc fixes 2025-07-17
Date: Sat, 19 Jul 2025 00:50:10 +0000 [thread overview]
Message-ID: <175288621044.2839493.14619363729044720272.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1752753970-261832-1-git-send-email-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 17 Jul 2025 15:06:08 +0300 you wrote:
> Hi,
>
> This small patchset provides misc bug fixes from the team to the mlx5
> driver.
>
> Thanks,
> Tariq.
>
> [...]
Here is the summary with links:
- [net,1/2] net/mlx5: Fix memory leak in cmd_exec()
https://git.kernel.org/netdev/net/c/3afa3ae3db52
- [net,2/2] net/mlx5: E-Switch, Fix peer miss rules to use peer eswitch
https://git.kernel.org/netdev/net/c/5b4c56ad4da0
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:[~2025-07-19 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 12:06 [PATCH net 0/2] mlx5 misc fixes 2025-07-17 Tariq Toukan
2025-07-17 12:06 ` [PATCH net 1/2] net/mlx5: Fix memory leak in cmd_exec() Tariq Toukan
2025-07-18 13:58 ` Simon Horman
2025-07-20 12:15 ` Markus Elfring
2025-07-17 12:06 ` [PATCH net 2/2] net/mlx5: E-Switch, Fix peer miss rules to use peer eswitch Tariq Toukan
2025-07-18 13:59 ` Simon Horman
2025-07-19 0:50 ` 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=175288621044.2839493.14619363729044720272.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=mbloch@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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