From: Jakub Kicinski <kuba@kernel.org>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Alex Vesker <valex@nvidia.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/mlx5: Use unique names for software steering caches
Date: Thu, 30 Jul 2026 07:09:12 -0700 [thread overview]
Message-ID: <20260730070912.3c7f24ed@kernel.org> (raw)
In-Reply-To: <3b0a153b-f47f-4260-b7d0-efef5ec0bca7@linux.ibm.com>
On Thu, 30 Jul 2026 15:30:08 +0200 Christian Borntraeger wrote:
> Am 23.07.26 um 15:13 schrieb Jakub Kicinski:
> > On Thu, 23 Jul 2026 09:45:39 +0300 Tariq Toukan wrote:
> >> Acked-by: Tariq Toukan <tariqt@nvidia.com>
>
> quick followup. I cannot find this in linux-next.
If the vendor's maintainer doesn't respond in reasonable time the patch
has to go via the vendor's tree. Tariq is expected to resubmit the
patch.
prev parent reply other threads:[~2026-07-30 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:22 [PATCH net] net/mlx5: Use unique names for software steering caches Leon Romanovsky
2026-07-15 9:14 ` Kalesh Anakkur Purayil
2026-07-15 9:19 ` Yevgeny Kliteynik
2026-07-16 6:57 ` Christian Borntraeger
2026-07-23 6:45 ` Tariq Toukan
2026-07-23 13:13 ` Jakub Kicinski
2026-07-30 13:30 ` Christian Borntraeger
2026-07-30 14:09 ` Jakub Kicinski [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=20260730070912.3c7f24ed@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kliteyn@nvidia.com \
--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=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=valex@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