From: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>
To: leon@kernel.org
Cc: dledford@redhat.com, haggaie@mellanox.com, jgg@ziepe.ca,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
prathameshdeshpande7@gmail.com
Subject: Re: [PATCH v9 0/2] IB/mlx5: Fix loopback rollback and locking
Date: Sun, 10 May 2026 23:35:06 +0100 [thread overview]
Message-ID: <20260510223519.6787-1-prathameshdeshpande7@gmail.com> (raw)
In-Reply-To: <20260510105531.GD15586@unreal>
On Sun, May 10, 2026 at 13:55:31 +0300, Leon Romanovsky wrote:
> On Fri, Apr 10, 2026 at 01:52:16AM +0100, Prathamesh Deshpande wrote:
> > Prathamesh Deshpande (2):
> > IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier
>
> I agree that this patch is needed.
>
> > IB/mlx5: Serialize force-enable state and preserve loopback accounting
>
> This change does not appear to be justified. The commit message provides no
> clear explanation of why it is needed.
>
> Thanks
Thanks, Leon.
v11 dropped the MP force-enable locking changes and kept MP helper behavior
unchanged. Patch 2 is now limited to the regular-path threshold/accounting
fixes.
I have also just sent a fresh v12 series that addresses your Patch 1
review regarding the missing mutex cleanups. You can find the updated
series here: https://lore.kernel.org/all/20260510222258.6654-1-prathameshdeshpande7@gmail.com/
prev parent reply other threads:[~2026-05-10 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 0:52 [PATCH v9 0/2] IB/mlx5: Fix loopback rollback and locking Prathamesh Deshpande
2026-04-10 0:52 ` [PATCH v9 1/2] IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier Prathamesh Deshpande
2026-05-10 10:56 ` Leon Romanovsky
2026-04-10 0:52 ` [PATCH v9 2/2] IB/mlx5: Serialize force-enable state and preserve loopback accounting Prathamesh Deshpande
2026-05-10 10:55 ` [PATCH v9 0/2] IB/mlx5: Fix loopback rollback and locking Leon Romanovsky
2026-05-10 22:35 ` Prathamesh Deshpande [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=20260510223519.6787-1-prathameshdeshpande7@gmail.com \
--to=prathameshdeshpande7@gmail.com \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.