linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeed@kernel.org>, Gal Pressman <gal@nvidia.com>,
	"Leon Romanovsky" <leon@kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"Tariq Toukan" <tariqt@nvidia.com>,
	Mark Bloch <mbloch@nvidia.com>, <netdev@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH net-next 0/5] net/mlx5: misc changes 2025-07-09
Date: Wed, 9 Jul 2025 00:16:22 +0300	[thread overview]
Message-ID: <1752009387-13300-1-git-send-email-tariqt@nvidia.com> (raw)

Hi,

This series contains misc enhancements to the mlx5 driver.

Regards,
Tariq


Carolina Jubran (1):
  net/mlx5e: Remove unused VLAN insertion logic in TX path

Cosmin Ratiu (1):
  net/mlx5e: CT: extract a memcmp from a spinlock section

Gal Pressman (1):
  net/mlx5e: Replace recursive VLAN push handling with an iterative loop

Maor Gottlieb (1):
  net/mlx5: Warn when write combining is not supported

Tariq Toukan (1):
  net/mlx5e: RX, Remove unnecessary RQT redirects

 drivers/net/ethernet/mellanox/mlx5/core/en.h  |  1 -
 .../net/ethernet/mellanox/mlx5/core/en/ptp.c  |  2 -
 .../mellanox/mlx5/core/en/reporter_tx.c       |  1 -
 .../ethernet/mellanox/mlx5/core/en/rx_res.c   |  4 +-
 .../mellanox/mlx5/core/en/tc/act/vlan.c       | 43 ++++++++++---------
 .../ethernet/mellanox/mlx5/core/en/tc_ct.c    |  5 ++-
 .../net/ethernet/mellanox/mlx5/core/en_main.c |  2 -
 .../net/ethernet/mellanox/mlx5/core/en_tx.c   |  9 +---
 drivers/net/ethernet/mellanox/mlx5/core/wc.c  |  3 ++
 9 files changed, 31 insertions(+), 39 deletions(-)


base-commit: 19c066f940666bf6c0982635e4441100ca8d75bc
-- 
2.31.1


             reply	other threads:[~2025-07-08 21:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 21:16 Tariq Toukan [this message]
2025-07-08 21:16 ` [PATCH net-next 1/5] net/mlx5e: Remove unused VLAN insertion logic in TX path Tariq Toukan
2025-07-09 17:23   ` Simon Horman
2025-07-08 21:16 ` [PATCH net-next 2/5] net/mlx5e: CT: extract a memcmp from a spinlock section Tariq Toukan
2025-07-09 17:24   ` Simon Horman
2025-07-08 21:16 ` [PATCH net-next 3/5] net/mlx5e: Replace recursive VLAN push handling with an iterative loop Tariq Toukan
2025-07-09 17:24   ` Simon Horman
2025-07-10  2:47   ` Jakub Kicinski
2025-07-08 21:16 ` [PATCH net-next 4/5] net/mlx5: Warn when write combining is not supported Tariq Toukan
2025-07-09 17:24   ` Simon Horman
2025-07-08 21:16 ` [PATCH net-next 5/5] net/mlx5e: RX, Remove unnecessary RQT redirects Tariq Toukan
2025-07-09 17:24   ` Simon Horman
2025-07-10  3:00 ` [PATCH net-next 0/5] net/mlx5: misc changes 2025-07-09 patchwork-bot+netdevbpf

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=1752009387-13300-1-git-send-email-tariqt@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --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 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).