[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB6PR0402MB27605875A6F85CE06790BD0E88510@DB6PR0402MB2760.eurprd04.prod.outlook.com>
Date: Mon, 31 Aug 2020 09:07:53 +0000
From: Peng Fan <peng.fan@....com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "rjw@...ysocki.net" <rjw@...ysocki.net>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"broonie@...nel.org" <broonie@...nel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: RE: [PATCH] cpufreq: dt: delay the clk/regulator check
> Subject: Re: [PATCH] cpufreq: dt: delay the clk/regulator check
>
> On 31-08-20, 16:48, peng.fan@....com wrote:
> > From: Peng Fan <peng.fan@....com>
> >
> > cpufreq_init could be used to do check clk/regulator check, there is
> > no need to duplicate the work in resources_available.
> >
> > Signed-off-by: Peng Fan <peng.fan@....com>
>
> Hi can you please see if this happens on linux-next as well ? The routine
> resources_available() isn't there anymore.
Not happen in Linux-next after I rebase.
Thanks,
Peng.
>
> --
> viresh
Powered by blists - more mailing lists