netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mark Bloch <mbloch@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>, <saeedm@nvidia.com>,
	<gal@nvidia.com>, <leonro@nvidia.com>, <tariqt@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>, <netdev@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Dragos Tatulea <dtatulea@nvidia.com>,
	"Cosmin Ratiu" <cratiu@nvidia.com>
Subject: Re: [PATCH net-next v4 09/11] net/mlx5e: Implement queue mgmt ops and single channel swap
Date: Wed, 11 Jun 2025 06:26:54 -0700	[thread overview]
Message-ID: <20250611062654.5121229b@kernel.org> (raw)
In-Reply-To: <20250610150950.1094376-10-mbloch@nvidia.com>

On Tue, 10 Jun 2025 18:09:48 +0300 Mark Bloch wrote:
> +	mdev = mlx5_sd_ch_ix_get_dev(priv->mdev, queue_index);
> +	err = mlx5e_build_channel_param(mdev, &params, &new->cparam);
> +	if (err) {
> +		return err;
> +		goto unlock;

missed this nugget yesterday, sorry..

> +	}

  reply	other threads:[~2025-06-11 13:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 15:09 [PATCH net-next v4 00/11] net/mlx5e: Add support for devmem and io_uring TCP zero-copy Mark Bloch
2025-06-10 15:09 ` [PATCH net-next v4 01/11] net: Allow const args for of page_to_netmem() Mark Bloch
2025-06-12  4:52   ` Mina Almasry
2025-06-12  8:06     ` [PATCH net-next v4 01/11] net: Allow const args for of page_to_netmem()y Dragos Tatulea
2025-06-10 15:09 ` [PATCH net-next v4 02/11] net: Add skb_can_coalesce for netmem Mark Bloch
2025-06-12  4:53   ` Mina Almasry
2025-06-10 15:09 ` [PATCH net-next v4 03/11] net/mlx5e: SHAMPO: Reorganize mlx5_rq_shampo_alloc Mark Bloch
2025-06-10 15:09 ` [PATCH net-next v4 04/11] net/mlx5e: SHAMPO: Remove redundant params Mark Bloch
2025-06-10 15:09 ` [PATCH net-next v4 05/11] net/mlx5e: SHAMPO: Improve hw gro capability checking Mark Bloch
2025-06-10 15:09 ` [PATCH net-next v4 06/11] net/mlx5e: SHAMPO: Separate pool for headers Mark Bloch
2025-06-10 15:09 ` [PATCH net-next v4 07/11] net/mlx5e: Convert over to netmem Mark Bloch
2025-06-12  5:11   ` Mina Almasry
2025-06-12  8:19     ` Dragos Tatulea
2025-06-10 15:09 ` [PATCH net-next v4 08/11] net/mlx5e: Add support for UNREADABLE netmem page pools Mark Bloch
2025-06-12  5:16   ` Mina Almasry
2025-06-12  8:46     ` Dragos Tatulea
2025-06-12 20:47       ` Mina Almasry
2025-06-10 15:09 ` [PATCH net-next v4 09/11] net/mlx5e: Implement queue mgmt ops and single channel swap Mark Bloch
2025-06-11 13:26   ` Jakub Kicinski [this message]
2025-06-10 15:09 ` [PATCH net-next v4 10/11] net/mlx5e: Support ethtool tcp-data-split settings Mark Bloch
2025-06-11 13:26   ` Jakub Kicinski
2025-06-10 15:09 ` [PATCH net-next v4 11/11] net/mlx5e: Add TX support for netmems Mark Bloch
2025-06-12  5:17   ` Mina Almasry

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=20250611062654.5121229b@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --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=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).