10 Jul
2014
10 Jul
'14
12:08 p.m.
On 10 July 2014 17:29, Borislav Petkov bp@alien8.de wrote:
On Thu, Jul 10, 2014 at 05:21:43PM +0530, Viresh Kumar wrote:
So that it appears in boot logs and we know cpufreq registered properly.
So flip that logic: Don't say anything in the success case and issue an error only when it failed. Like the rest of the code does it.
The problem with that is: CPUFreq may not be compiled in at all and we wouldn't know the difference between success and absence.
And so tried to add a print, like any other driver would do.