On 10 July 2014 17:29, Borislav Petkov <b...@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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
