[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154947990848.115909.478174902516192562@swboyd.mtv.corp.google.com>
Date: Wed, 06 Feb 2019 11:05:08 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: akshu.agrawal@....com, andrew.smirnov@...il.com,
b.zolnierkie@...sung.com, corbet@....net, cw00.choi@...sung.com,
djkurtz@...omium.org, krzk@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux@...linux.org.uk, linux@...ck-us.net,
matti.vaittinen@...rohmeurope.com, mazziesaccount@...il.com,
mturquette@...libre.com, pavel@....cz, pombredanne@...b.com,
rafael.j.wysocki@...el.com, sjhuang@...vatar.ai, sre@...nel.org,
vkoul@...nel.org
Subject: Re: [PATCH v7 2/3] clk: clk-max77686: Clean clkdev lookup leak and use devm
Quoting Matti Vaittinen (2018-12-07 03:10:15)
> clk-max77686 never clean clkdev lookup at remove. This can cause
> oops if clk-max77686 is removed and inserted again. Fix leak by
> using new devm clkdev lookup registration. Simplify also error
> path by using new devm_of_clk_add_hw_provider.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
> Reviewed-by: Krzysztof Kozlowski <krzk@...nel.org>
> ---
Applied to clk-next
Powered by blists - more mailing lists