From: Jiabing Wan <wanjiabing@vivo.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jia-Wei Chang <jia-wei.chang@mediatek.com>,
"Andrew-sh.Cheng" <andrew-sh.cheng@mediatek.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] cpufreq: mediatek: Fix potential deadlock problem in mtk_cpufreq_set_target
Date: Tue, 10 May 2022 17:36:45 +0800 [thread overview]
Message-ID: <e58f36d3-c01d-b133-6615-be5d34fa62a1@vivo.com> (raw)
In-Reply-To: <20220510092822.j3z6bydurg7x5bu4@vireshk-i7>
On 2022/5/10 17:28, Viresh Kumar wrote:
> On 10-05-22, 17:23, Jiabing Wan wrote:
>>
>> On 2022/5/10 17:12, Viresh Kumar wrote:
>>> On 10-05-22, 17:05, Wan Jiabing wrote:
>>>> Fix following coccichek error:
>>>> ./drivers/cpufreq/mediatek-cpufreq.c:199:2-8: preceding lock on line
>>>> ./drivers/cpufreq/mediatek-cpufreq.c:208:2-8: preceding lock on line
>>>>
>>>> mutex_lock is acquired but not released before return.
>>>> Use 'goto out' to help releasing the mutex_lock.
>>>>
>>>> Fixes: c210063b40ac ("cpufreq: mediatek: Add opp notification support")
>>>> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
>>> You should have added the review tag you received.
>>>
>>> Applied. Thanks.
>> Oh, yes. I would add the "Reviewed-by:" tag only if someone sends
>> this tag to me.
> Didn't you get this ?
>
> https://lore.kernel.org/linux-mediatek/304e7eefbb57e9c938737b64fbb515201c7944b8.camel@mediatek.com/
Oh, sorry! there might be some problem in my email-server.
I didn't get this email and I also didn't see this email on LKML lore.
So I missed this email.
Sorry for my mistake.
Wan Jiabing
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-10 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:05 [PATCH v2] cpufreq: mediatek: Fix potential deadlock problem in mtk_cpufreq_set_target Wan Jiabing
2022-05-10 9:12 ` Viresh Kumar
2022-05-10 9:23 ` Jiabing Wan
2022-05-10 9:28 ` Viresh Kumar
2022-05-10 9:36 ` Jiabing Wan [this message]
2022-05-10 11:23 ` Rex-BC Chen
2022-05-11 3:11 ` Viresh Kumar
2022-05-11 3:23 ` Rex-BC Chen
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=e58f36d3-c01d-b133-6615-be5d34fa62a1@vivo.com \
--to=wanjiabing@vivo.com \
--cc=andrew-sh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jia-wei.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=rex-bc.chen@mediatek.com \
--cc=viresh.kumar@linaro.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