[PATCH] Abort powerd when no cpufreq(4) support is found

[Nate Lawson]

The message is fine, but I think an error code of 0 is wrong. Powerd didn't start, whereas 0 means the daemon launched successfully.

On Apr 9, 2012, at 2:11 AM, Robert Millan wrote:

> Hi,
> 
> I'd like to check-in this patch so that powerd aborts gracefully when
> there's no cpufreq(4) support for the CPU in which it is running.
> 
> Does this look alright?
> 
> -- 
> Robert Millan
> <no_cpufreq.diff>