[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220510091212.olrvvjlx4jtm7zw2@vireshk-i7>
Date: Tue, 10 May 2022 14:42:12 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Wan Jiabing <wanjiabing@...o.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Rex-BC Chen <rex-bc.chen@...iatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Jia-Wei Chang <jia-wei.chang@...iatek.com>,
"Andrew-sh.Cheng" <andrew-sh.cheng@...iatek.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v2] cpufreq: mediatek: Fix potential deadlock problem in
mtk_cpufreq_set_target
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@...o.com>
You should have added the review tag you received.
Applied. Thanks.
--
viresh
Powered by blists - more mailing lists