[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200901101221.fmjjrmbbzrnqdgos@vireshk-i7>
Date: Tue, 1 Sep 2020 15:42:21 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: ulf.hansson@...aro.org, "Rafael J. Wysocki" <rjw@...ysocki.net>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...nel.org>, Nishanth Menon <nm@...com>,
nks@...wful.org, georgi.djakov@...aro.org,
Stephan Gerhold <stephan@...hold.net>,
linux-kernel@...r.kernel.org,
'Linux Samsung SOC' <linux-samsung-soc@...r.kernel.org>,
Krzysztof Kozlowski <krzk@...nel.org>
Subject: Re: [PATCH V2 2/2] cpufreq: dt: Refactor initialization to handle
probe deferral properly
On 01-09-20, 12:05, Marek Szyprowski wrote:
> Indeed, this patch seems to fix/hide that warning. Feel free to add:
s/hide/really-fix/ :)
I assumed that this problem is going to be there, when I applied the
other patch and so was trying to write a fix but somehow skipped doing
that :(
--
viresh
Powered by blists - more mailing lists