From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Cc: Joe Damato <jdamato@fastly.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
tariqt@nvidia.com, Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"open list:MELLANOX MLX5 core VPI driver"
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH net-next v2] eth: mlx5: link NAPI instances to queues and IRQs
Date: Mon, 05 Feb 2024 21:09:19 -0800 [thread overview]
Message-ID: <87jznikwe9.fsf@nvidia.com> (raw)
In-Reply-To: <87o7cul2nf.fsf@nvidia.com>
On Mon, 05 Feb, 2024 18:52:45 -0800 Rahul Rameshbabu <rrameshbabu@nvidia.com> wrote:
> On Tue, 06 Feb, 2024 02:49:56 +0000 Joe Damato <jdamato@fastly.com> wrote:
>> Make mlx5 compatible with the newly added netlink queue GET APIs.
>>
>> v1 -> v2:
>> - Move netlink NULL code to mlx5e_deactivate_channel
>> - Move netif_napi_set_irq to mlx5e_open_channel and avoid storing the
>> irq, after netif_napi_add which itself sets the IRQ to -1.
>> - Fix white space where IRQ is stored in mlx5e_open_channel
Also, the changelog should not be part of the commit description since
it will not make much sense once the final version is accepted. You can
either manually paste the changelog in a section of the patch that will
not be applied by git or use git notes to annotate the changelog.
* https://git-scm.com/docs/git-notes
* https://git-scm.com/docs/git-format-patch#Documentation/git-format-patch.txt---notesltrefgt
>>
>> Signed-off-by: Joe Damato <jdamato@fastly.com>
>> ---
--
Thanks,
Rahul Rameshbabu
prev parent reply other threads:[~2024-02-06 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 2:49 [PATCH net-next v2] eth: mlx5: link NAPI instances to queues and IRQs Joe Damato
2024-02-06 2:52 ` Rahul Rameshbabu
2024-02-06 5:09 ` Rahul Rameshbabu [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=87jznikwe9.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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).