From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Yajun Deng <yajun.deng@linux.dev>
Subject: Re: [PATCH rdma-next] Revert "RDMA/core: Fix ib_qp_usecnt_dec() called when error"
Date: Mon, 14 Mar 2022 20:44:50 -0300 [thread overview]
Message-ID: <20220314234450.GC172564@nvidia.com> (raw)
In-Reply-To: <74c11029adaf449b3b9228a77cc82f39e9e892c8.1646851220.git.leonro@nvidia.com>
On Wed, Mar 09, 2022 at 08:42:13PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> This reverts commit 7c4a539ec38f4ce400a0f3fcb5ff6c940fcd67bb. which
> causes to the following error in mlx4.
Dare I ask why this happens?
Applied to for-next
Thanks,
Jason
next prev parent reply other threads:[~2022-03-14 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 18:42 [PATCH rdma-next] Revert "RDMA/core: Fix ib_qp_usecnt_dec() called when error" Leon Romanovsky
2022-03-10 6:12 ` Yajun Deng
2022-03-10 9:48 ` Leon Romanovsky
2022-03-10 10:05 ` Yajun Deng
2022-03-14 23:44 ` Jason Gunthorpe [this message]
2022-03-16 8:12 ` Leon Romanovsky
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=20220314234450.GC172564@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yajun.deng@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