From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>, Simon Horman <horms@kernel.org>
Cc: Alexandre Cassen <acassen@corp.free.fr>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net/mlx5: HWS, fix pool creation races
Date: Mon, 19 Oct 2026 18:51:04 -0700 [thread overview]
Message-ID: <20261019185104.7a2135c3@kernel.org> (raw)
In-Reply-To: <09192a25-f141-4a88-bc5e-ffda957da554@nvidia.com>
On Mon, 19 Oct 2026 14:25:38 +0300 Tariq Toukan wrote:
> Acked-by: Tariq Toukan <tariqt@nvidia.com>
Clashiko keeps saying that the problem solved by patch 1 doesn't
actually exist, could one of the reviewers of this series pls
confirm that the AI analysis is wrong? The commit msg says
the problem itself was found by AI, so is it not a hallucination?
next prev parent reply other threads:[~2026-10-20 1:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 10:05 [PATCH net v2 0/2] net/mlx5: HWS, fix pool creation races Alexandre Cassen
2026-10-12 10:05 ` [PATCH net v2 1/2] net/mlx5: HWS, fix reformat pool creation race Alexandre Cassen
2026-10-13 10:08 ` sashiko-bot
2026-10-13 10:25 ` netdev-bot+sashiko
2026-10-18 14:18 ` Simon Horman
2026-10-12 10:05 ` [PATCH net v2 2/2] net/mlx5: HWS, fix modify header " Alexandre Cassen
2026-10-12 18:03 ` Moshe Shemesh
2026-10-13 10:08 ` sashiko-bot
2026-10-18 14:18 ` Simon Horman
2026-10-19 11:25 ` [PATCH net v2 0/2] net/mlx5: HWS, fix pool creation races Tariq Toukan
2026-10-20 1:51 ` Jakub Kicinski [this message]
2026-10-20 10:10 ` Moshe Shemesh
2026-10-20 11:10 ` 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=20261019185104.7a2135c3@kernel.org \
--to=kuba@kernel.org \
--cc=acassen@corp.free.fr \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kliteyn@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@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