From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: ajd@linux.ibm.com, arnd@arndb.de, fbarrat@linux.ibm.com,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 -next] misc: ocxl: use DEFINE_MUTEX() for mutex lock
Date: Wed, 3 Feb 2021 22:40:51 +1100 (AEDT) [thread overview]
Message-ID: <161235199985.1516112.15428721712671016806.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20201224132446.31286-1-zhengyongjun3@huawei.com>
On Thu, 24 Dec 2020 21:24:46 +0800, Zheng Yongjun wrote:
> mutex lock can be initialized automatically with DEFINE_MUTEX()
> rather than explicitly calling mutex_init().
Applied to powerpc/next.
[1/1] ocxl: use DEFINE_MUTEX() for mutex lock
https://git.kernel.org/powerpc/c/52f6b0a90bcf573ba8a33e97544c7b6f292376a4
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: fbarrat@linux.ibm.com, gregkh@linuxfoundation.org,
ajd@linux.ibm.com, arnd@arndb.de
Subject: Re: [PATCH v2 -next] misc: ocxl: use DEFINE_MUTEX() for mutex lock
Date: Wed, 3 Feb 2021 22:40:51 +1100 (AEDT) [thread overview]
Message-ID: <161235199985.1516112.15428721712671016806.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20201224132446.31286-1-zhengyongjun3@huawei.com>
On Thu, 24 Dec 2020 21:24:46 +0800, Zheng Yongjun wrote:
> mutex lock can be initialized automatically with DEFINE_MUTEX()
> rather than explicitly calling mutex_init().
Applied to powerpc/next.
[1/1] ocxl: use DEFINE_MUTEX() for mutex lock
https://git.kernel.org/powerpc/c/52f6b0a90bcf573ba8a33e97544c7b6f292376a4
cheers
next prev parent reply other threads:[~2021-02-03 11:42 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
2021-01-05 21:53 ` Andrew Donnellan
2021-02-03 11:40 ` Michael Ellerman [this message]
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=161235199985.1516112.15428721712671016806.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=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.