Messages in this thread | | | Date | Tue, 16 Jul 2019 13:11:30 +0200 | From | Niklas Cassel <> | Subject | Re: [PATCH 02/13] cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs |
| |
On Wed, Jul 10, 2019 at 11:48:39AM +0530, Viresh Kumar wrote: > On 05-07-19, 11:57, Niklas Cassel wrote: > > -static struct platform_driver qcom_cpufreq_kryo_driver = { > > - .probe = qcom_cpufreq_kryo_probe, > > - .remove = qcom_cpufreq_kryo_remove, > > +static struct platform_driver qcom_cpufreq_driver = { > > + .probe = qcom_cpufreq_probe, > > + .remove = qcom_cpufreq_remove, > > .driver = { > > - .name = "qcom-cpufreq-kryo", > > + .name = "qcom-cpufreq", > > Should we still name it "qcom-cpufreq-nvmem" here ? Only the string > here.
Sure, I can fix this in next version.
Kind regards, Niklas
> > > }, > > }; > > -- > viresh
| |