From: Leon Romanovsky <leon@kernel.org>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
dledford@redhat.com, jgg@ziepe.ca
Subject: Re: [PATCH v2 -next] mlx5: use DEFINE_MUTEX() for mutex lock
Date: Sun, 27 Dec 2020 07:58:24 +0200 [thread overview]
Message-ID: <20201227055824.GA4457@unreal> (raw)
In-Reply-To: <20201224132323.31126-1-zhengyongjun3@huawei.com>
On Thu, Dec 24, 2020 at 09:23:23PM +0800, Zheng Yongjun wrote:
> mutex lock can be initialized automatically with DEFINE_MUTEX()
> rather than explicitly calling mutex_init().
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
> ---
> drivers/infiniband/hw/mlx5/main.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
As I wrote earlier, this patch can't be applied, because the xlt_emergency_page_mutex
mutex was moved in the commit f22c30aa6d27 ("RDMA/mlx5: Move xlt_emergency_page_mutex into mr.c")
Thanks
prev parent reply other threads:[~2020-12-27 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 13:23 [PATCH v2 -next] mlx5: use DEFINE_MUTEX() for mutex lock Zheng Yongjun
2020-12-27 5:58 ` Leon Romanovsky [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=20201227055824.GA4457@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zhengyongjun3@huawei.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