From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Chaehyun Lim <chaehyun.lim@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ath6kl@lists.infradead.org" <ath6kl@lists.infradead.org>
Subject: Re: [PATCH V2 2/2] ath6kl: replace semaphore with mutex
Date: Wed, 22 Jun 2016 08:59:59 +0000 [thread overview]
Message-ID: <87h9cliooi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160621232210.5801-1-chaehyun.lim@gmail.com> (Chaehyun Lim's message of "Wed, 22 Jun 2016 08:22:10 +0900")
(Adding ath6k list)
Chaehyun Lim <chaehyun.lim@gmail.com> writes:
> It replaces struct semaphore sem with struct mutex mutex
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Chaehyun Lim <chaehyun.lim@gmail.com>
> ---
> V2: fix build failure reported by kbuild test robot
I don't think Reported-by is correct, it should be only used when
reporting the original issue
Have you tested this on a real device? I'm reluctant to apply this big
locking change without some level of testing.
--
Kalle Valo
prev parent reply other threads:[~2016-06-22 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:22 [PATCH V2 2/2] ath6kl: replace semaphore with mutex Chaehyun Lim
2016-06-22 8:59 ` Valo, Kalle [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=87h9cliooi.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl@lists.infradead.org \
--cc=chaehyun.lim@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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