From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: [pull request][net 0/7] mlx5 fixes 2024-09-09
Date: Mon, 9 Sep 2024 12:44:58 -0700 [thread overview]
Message-ID: <20240909194505.69715-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
This series provides bug fixes to mlx5 driver.
Please pull and let me know if there is any problem.
Thanks,
Saeed.
The following changes since commit b3c9e65eb227269ed72a115ba22f4f51b4e62b4d:
net: hsr: remove seqnr_lock (2024-09-09 10:25:01 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-fixes-2024-09-09
for you to fetch changes up to b1d305abef4640af1b4f1b4774d513cd81b10cfc:
net/mlx5: Fix bridge mode operations when there are no VFs (2024-09-09 12:39:57 -0700)
----------------------------------------------------------------
mlx5-fixes-2024-09-09
----------------------------------------------------------------
Benjamin Poirier (1):
net/mlx5: Fix bridge mode operations when there are no VFs
Carolina Jubran (3):
net/mlx5: Explicitly set scheduling element and TSAR type
net/mlx5: Add missing masks and QoS bit masks for scheduling elements
net/mlx5: Verify support for scheduling element and TSAR type
Maher Sanalla (1):
net/mlx5: Update the list of the PCI supported devices
Shahar Shitrit (2):
net/mlx5e: Add missing link modes to ptys2ethtool_map
net/mlx5e: Add missing link mode to ptys2ext_ethtool_map
.../net/ethernet/mellanox/mlx5/core/en_ethtool.c | 10 +++++
.../net/ethernet/mellanox/mlx5/core/esw/legacy.c | 4 +-
drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c | 51 +++++++++++++---------
drivers/net/ethernet/mellanox/mlx5/core/main.c | 1 +
drivers/net/ethernet/mellanox/mlx5/core/qos.c | 7 +++
include/linux/mlx5/mlx5_ifc.h | 10 ++++-
6 files changed, 60 insertions(+), 23 deletions(-)
next reply other threads:[~2024-09-09 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 19:44 Saeed Mahameed [this message]
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
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=20240909194505.69715-1-saeed@kernel.org \
--to=saeed@kernel.org \
--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 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).