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, gal@nvidia.com, leonro@nvidia.com,
msanalla@nvidia.com
Subject: Re: [net 1/7] net/mlx5: Update the list of the PCI supported devices
Date: Wed, 11 Sep 2024 03:20:32 +0000 [thread overview]
Message-ID: <172602483277.473764.10914302582891504021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240909194505.69715-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Mon, 9 Sep 2024 12:44:59 -0700 you wrote:
> From: Maher Sanalla <msanalla@nvidia.com>
>
> Add the upcoming ConnectX-9 device ID to the table of supported
> PCI device IDs.
>
> Fixes: f908a35b2218 ("net/mlx5: Update the list of the PCI supported devices")
> Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
> Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,1/7] net/mlx5: Update the list of the PCI supported devices
https://git.kernel.org/netdev/net/c/7472d157cb80
- [net,2/7] net/mlx5e: Add missing link modes to ptys2ethtool_map
https://git.kernel.org/netdev/net/c/7617d62cba4a
- [net,3/7] net/mlx5e: Add missing link mode to ptys2ext_ethtool_map
https://git.kernel.org/netdev/net/c/80bf474242b2
- [net,4/7] net/mlx5: Explicitly set scheduling element and TSAR type
https://git.kernel.org/netdev/net/c/c88146abe4d0
- [net,5/7] net/mlx5: Add missing masks and QoS bit masks for scheduling elements
https://git.kernel.org/netdev/net/c/452ef7f86036
- [net,6/7] net/mlx5: Verify support for scheduling element and TSAR type
https://git.kernel.org/netdev/net/c/861cd9b9cb62
- [net,7/7] net/mlx5: Fix bridge mode operations when there are no VFs
https://git.kernel.org/netdev/net/c/b1d305abef46
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:[~2024-09-11 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 19:44 [pull request][net 0/7] mlx5 fixes 2024-09-09 Saeed Mahameed
2024-09-09 19:44 ` [net 1/7] net/mlx5: Update the list of the PCI supported devices Saeed Mahameed
2024-09-11 3:20 ` patchwork-bot+netdevbpf [this message]
2024-09-09 19:45 ` [net 2/7] net/mlx5e: Add missing link modes to ptys2ethtool_map Saeed Mahameed
2024-09-09 19:45 ` [net 3/7] net/mlx5e: Add missing link mode to ptys2ext_ethtool_map Saeed Mahameed
2024-09-09 19:45 ` [net 4/7] net/mlx5: Explicitly set scheduling element and TSAR type Saeed Mahameed
2024-09-09 19:45 ` [net 5/7] net/mlx5: Add missing masks and QoS bit masks for scheduling elements Saeed Mahameed
2024-09-09 19:45 ` [net 6/7] net/mlx5: Verify support for scheduling element and TSAR type Saeed Mahameed
2024-09-09 19:45 ` [net 7/7] net/mlx5: Fix bridge mode operations when there are no VFs 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=172602483277.473764.10914302582891504021.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--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 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).