From: Jacob Keller <jacob.e.keller@intel.com>
To: Joe Damato <jdamato@fastly.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Cc: <nalramli@fastly.com>, <mkarsten@uwaterloo.ca>,
Jakub Kicinski <kuba@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"open list:MELLANOX MLX4 core VPI driver"
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH net-next v6 2/3] net/mlx4: link NAPI instances to queues and IRQs
Date: Thu, 30 May 2024 14:10:03 -0700 [thread overview]
Message-ID: <b69ba9a0-3054-42f4-8476-8782f56db4bd@intel.com> (raw)
In-Reply-To: <20240528181139.515070-3-jdamato@fastly.com>
On 5/28/2024 11:11 AM, Joe Damato wrote:
> Make mlx4 compatible with the newly added netlink queue GET APIs.
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> Tested-by: Martin Karsten <mkarsten@uwaterloo.ca>
> Acked-by: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
> ---
Straight forward and easy implementation. Nice.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-05-30 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 18:11 [PATCH net-next v6 0/3] mlx4: Add support for netdev-genl API Joe Damato
2024-05-28 18:11 ` [PATCH net-next v6 1/3] net/mlx4: Track RX allocation failures in a stat Joe Damato
2024-05-30 21:08 ` Jacob Keller
2024-05-30 21:12 ` Jacob Keller
2024-05-28 18:11 ` [PATCH net-next v6 2/3] net/mlx4: link NAPI instances to queues and IRQs Joe Damato
2024-05-30 21:10 ` Jacob Keller [this message]
2024-05-28 18:11 ` [PATCH net-next v6 3/3] net/mlx4: support per-queue statistics via netlink Joe Damato
2024-05-30 21:11 ` Jacob Keller
2024-05-31 0:20 ` [PATCH net-next v6 0/3] mlx4: Add support for netdev-genl API 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=b69ba9a0-3054-42f4-8476-8782f56db4bd@intel.com \
--to=jacob.e.keller@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=nalramli@fastly.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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