[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5303C31C.4070607@wwwdotorg.org>
Date: Tue, 18 Feb 2014 13:31:24 -0700
From: Stephen Warren <swarren@...dotorg.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nishanth Menon <nm@...com>, Kgene Kim <kgene.kim@...sung.com>,
jinchoi@...adcom.com, Lan Tianyu <tianyu.lan@...el.com>,
Sebastian Capella <sebastian.capella@...aro.org>,
Jonghwan Choi <jhbird.choi@...sung.com>
Subject: Re: [PATCH V5 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
On 02/16/2014 11:02 PM, Viresh Kumar wrote:
> On 15 February 2014 01:52, Stephen Warren <swarren@...dotorg.org> wrote:
>> BTW, I also happened to test these on a Tegra114 system, on which there
>> is no cpufreq driver, and this series (applied on top of commit
>> 9398a10cd964 Merge tag 'regulator-v3.14-rc2') causes the following
>> during suspend:
>
> Ahh, that's a obvious bug. Following would fix it, thanks:
Yes, I tested V6 of the patch series, which incorporates that change,
and it's OK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists