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, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, shayd@nvidia.com, moshe@nvidia.com
Subject: Re: [net 1/5] net/mlx5: Remove rmap also in case dynamic MSIX not supported
Date: Thu, 01 Jun 2023 17:20:22 +0000 [thread overview]
Message-ID: <168564002233.14862.10848012612929831667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230601031051.131529-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Wed, 31 May 2023 20:10:47 -0700 you wrote:
> From: Shay Drory <shayd@nvidia.com>
>
> mlx5 add IRQs to rmap upon MSIX request, and mlx5 remove rmap from
> MSIX only if msi_map.index is populated. However, msi_map.index is
> populated only when dynamic MSIX is supported. This results in freeing
> IRQs without removing them from rmap, which triggers the bellow
> WARN_ON[1].
>
> [...]
Here is the summary with links:
- [net,1/5] net/mlx5: Remove rmap also in case dynamic MSIX not supported
https://git.kernel.org/netdev/net/c/1c4c769cdf68
- [net,2/5] net/mlx5: Fix setting of irq->map.index for static IRQ case
https://git.kernel.org/netdev/net/c/8764bd0fa5d4
- [net,3/5] net/mlx5: Ensure af_desc.mask is properly initialized
https://git.kernel.org/netdev/net/c/368591995d01
- [net,4/5] net/mlx5e: Fix error handling in mlx5e_refresh_tirs
https://git.kernel.org/netdev/net/c/b6193d7030e3
- [net,5/5] net/mlx5: Read embedded cpu after init bit cleared
https://git.kernel.org/netdev/net/c/bbfa4b58997e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-06-01 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 3:10 [pull request][net 0/5] mlx5 fixes 2023-05-31 Saeed Mahameed
2023-06-01 3:10 ` [net 1/5] net/mlx5: Remove rmap also in case dynamic MSIX not supported Saeed Mahameed
2023-06-01 17:20 ` patchwork-bot+netdevbpf [this message]
2023-06-01 3:10 ` [net 2/5] net/mlx5: Fix setting of irq->map.index for static IRQ case Saeed Mahameed
2023-06-01 3:10 ` [net 3/5] net/mlx5: Ensure af_desc.mask is properly initialized Saeed Mahameed
2023-06-01 3:10 ` [net 4/5] net/mlx5e: Fix error handling in mlx5e_refresh_tirs Saeed Mahameed
2023-06-01 3:10 ` [net 5/5] net/mlx5: Read embedded cpu after init bit cleared Saeed Mahameed
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=168564002233.14862.10848012612929831667.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=shayd@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 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).