From: Kalle Valo <kvalo@codeaurora.org>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Zheng Yongjun <zhengyongjun3@huawei.com>
Subject: Re: [PATCH v2 -next] atmel: at76c50x: use DEFINE_MUTEX() for mutex lock
Date: Mon, 8 Feb 2021 11:15:08 +0000 (UTC) [thread overview]
Message-ID: <20210208111508.A96D5C43461@smtp.codeaurora.org> (raw)
In-Reply-To: <20201224132456.31341-1-zhengyongjun3@huawei.com>
Zheng Yongjun <zhengyongjun3@huawei.com> wrote:
> mutex lock can be initialized automatically with DEFINE_MUTEX()
> rather than explicitly calling mutex_init().
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
Patch applied to wireless-drivers-next.git, thanks.
ae30a740a176 atmel: at76c50x: use DEFINE_MUTEX() for mutex lock
--
https://patchwork.kernel.org/project/linux-wireless/patch/20201224132456.31341-1-zhengyongjun3@huawei.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-02-08 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 13:24 [PATCH v2 -next] atmel: at76c50x: use DEFINE_MUTEX() for mutex lock Zheng Yongjun
2021-02-08 11:15 ` Kalle Valo [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=20210208111508.A96D5C43461@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).