From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <jdamato@fastly.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
tariqt@nvidia.com, rrameshbabu@nvidia.com, saeedm@nvidia.com,
leon@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
gal@nvidia.com, vadim.fedorenko@linux.dev,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v4] net/mlx5e: link NAPI instances to queues and IRQs
Date: Tue, 13 Feb 2024 01:00:28 +0000 [thread overview]
Message-ID: <170778602817.24441.17425446527268970551.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240209202312.30181-1-jdamato@fastly.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Feb 2024 20:23:08 +0000 you wrote:
> Make mlx5 compatible with the newly added netlink queue GET APIs.
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> ---
> v3 -> v4:
> - Use sq->netdev and sq->cq.napi to get the netdev and NAPI structures in
> mlx5e_activate_txqsq and mlx5e_deactivate_txqsq as requested by Tariq
> Toukan [1]
> - Only set or unset NETDEV_QUEUE_TYPE_RX when the MLX5E_PTP_STATE_RX bit
> is on in mlx5e_ptp_activate_channel and mlx5e_ptp_deactivate_channel as
> requested by Rahul Rameshbabu [2]
>
> [...]
Here is the summary with links:
- [net-next,v4] net/mlx5e: link NAPI instances to queues and IRQs
https://git.kernel.org/netdev/net-next/c/f25e7b82635f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-13 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 20:23 [PATCH net-next v4] net/mlx5e: link NAPI instances to queues and IRQs Joe Damato
2024-02-10 7:01 ` Tariq Toukan
2024-02-13 1:00 ` patchwork-bot+netdevbpf [this message]
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=170778602817.24441.17425446527268970551.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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