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

2012-04-09 Thread 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 ___

Expand support ACPI button

2012-04-09 Thread Slawa Olhovchenkov
I have FSC Lifebook. I need support for some buutons. After compiling kernel w/ ACPI_DEBUG and enable some debug I got next messages in dmesg (after pressing button). What I can do next? Is this information enough? = evsci-0081 [234429] EvSciXruptHandler : Entry evgpe-0726

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

2012-04-09 Thread 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

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

2012-04-09 Thread 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

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

2012-04-09 Thread Doug Barton
On 04/09/2012 13:59, Robert Millan wrote: El 9 d’abril de 2012 18:53, Nate Lawson n...@root.org ha escrit: Fine by me. The rc framework or user should be the one to interpret the error code and realize that it's ok that it's not running (not supported). Committed then, thanks for reviewing.