From: Andrew Donnellan <ajd@linux.ibm.com>
To: Zheng Yongjun <zhengyongjun3@huawei.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: fbarrat@linux.ibm.com, arnd@arndb.de, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 -next] misc: ocxl: use DEFINE_MUTEX() for mutex lock
Date: Wed, 6 Jan 2021 08:53:28 +1100 [thread overview]
Message-ID: <9cfa9da6-39e1-58f3-c11d-ac2b0f8ca2b1@linux.ibm.com> (raw)
In-Reply-To: <20201224132446.31286-1-zhengyongjun3@huawei.com>
On 25/12/20 12:24 am, 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>
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Donnellan <ajd@linux.ibm.com>
To: Zheng Yongjun <zhengyongjun3@huawei.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: fbarrat@linux.ibm.com, gregkh@linuxfoundation.org, arnd@arndb.de
Subject: Re: [PATCH v2 -next] misc: ocxl: use DEFINE_MUTEX() for mutex lock
Date: Wed, 6 Jan 2021 08:53:28 +1100 [thread overview]
Message-ID: <9cfa9da6-39e1-58f3-c11d-ac2b0f8ca2b1@linux.ibm.com> (raw)
In-Reply-To: <20201224132446.31286-1-zhengyongjun3@huawei.com>
On 25/12/20 12:24 am, 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>
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2021-01-05 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 13:24 [PATCH v2 -next] misc: ocxl: use DEFINE_MUTEX() for mutex lock Zheng Yongjun
2020-12-24 13:24 ` Zheng Yongjun
2021-01-04 8:50 ` Frederic Barrat
2021-01-04 8:50 ` Frederic Barrat
2021-01-05 21:53 ` Andrew Donnellan [this message]
2021-01-05 21:53 ` Andrew Donnellan
2021-02-03 11:40 ` Michael Ellerman
2021-02-03 11:40 ` Michael Ellerman
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=9cfa9da6-39e1-58f3-c11d-ac2b0f8ca2b1@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.