From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, jgg@nvidia.com, saeedm@nvidia.com,
linux-rdma@vger.kernel.org, leonro@nvidia.com,
netdev@vger.kernel.org
Subject: Re: pull-request: mlx5-next netdev notifier deadlock 2023-02-07
Date: Thu, 09 Feb 2023 05:10:18 +0000 [thread overview]
Message-ID: <167591941843.2876.6131720358641221887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230208005626.72930-1-saeed@kernel.org>
Hello:
This pull request was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Feb 2023 16:56:26 -0800 you wrote:
> The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:
>
> Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git tags/mlx5-next-netdev-deadlock
>
> [...]
Here is the summary with links:
- pull-request: mlx5-next netdev notifier deadlock 2023-02-07
https://git.kernel.org/netdev/net-next/c/9245b518c89f
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:[~2023-02-09 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 0:56 pull-request: mlx5-next netdev notifier deadlock 2023-02-07 Saeed Mahameed
2023-02-09 3:12 ` Jakub Kicinski
2023-02-09 3:16 ` Jakub Kicinski
2023-02-09 3:46 ` Saeed Mahameed
2023-02-09 4:27 ` Jakub Kicinski
2023-02-09 4:51 ` Saeed Mahameed
2023-02-09 3:42 ` Saeed Mahameed
2023-02-09 5:10 ` 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=167591941843.2876.6131720358641221887.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@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.