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

[Robert Millan]

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
Description: Binary data
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

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

[Robert Millan]

Hi Nate,

El 9 d’abril de 2012 18:06, Nate Lawson n...@root.org ha escrit:
 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.

In that case, may I suggest that we return one of the error codes
recommended by sysexists(3)?  EX_UNAVAILABLE seems close enough to the
reason we're aborting.

-- 
Robert Millan


no_cpufreq.diff
Description: Binary data
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org