On Mon, May 24, 2021 at 02:47:15PM +0530, Viresh Kumar wrote: > On 21-05-21, 16:24, Sudeep Holla wrote: > > On Fri, May 21, 2021 at 09:38:34AM +0530, Viresh Kumar wrote: > > > On 20-05-21, 14:43, Rob Herring wrote: > > > > Not allowed because I can't turn this check on by default until we get > > > > rid of the existing 80 or so. But it is a new check and Viresh already > > > > applied, so oh well. > > > > > > I can always drop it :) > > > > > > > While I really don't care(evident by rate at which I worked on this 😉) > > I think Hector Yuan won't be happy to wait I guess. As a quick fix, you > > can update "qcom,cpufreq-hw" to "mediatek,cpufreq-hw". You will still > > get warning with this patch + update alone, but once you have Hector's > > mediatek cpufreq driver applied, the warnings must disappear. > > > > What do you think ? > > I guess you can send a fix later then. Sure 😄 -- Regards, Sudeep
