Date: Mon, 9 Apr 2012 09:06:14 -0700 From: Nate Lawson <nate@root.org> To: Robert Millan <rmh@freebsd.org> Cc: freebsd-acpi@freebsd.org, Steven Chamberlain <steven@pyro.eu.org> Subject: Re: [PATCH] Abort powerd when no cpufreq(4) support is found Message-ID: <E2E769FA-970A-4E1C-805B-DE6397B456C9@root.org> In-Reply-To: <CAOfDtXO=7ALiBVHdY-hHa158yXoM%2BXXigkU4SObPHRr0h-2iUQ@mail.gmail.com> References: <CAOfDtXO=7ALiBVHdY-hHa158yXoM%2BXXigkU4SObPHRr0h-2iUQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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, >=20 > 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. >=20 > Does this look alright? >=20 > --=20 > Robert Millan > <no_cpufreq.diff>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E2E769FA-970A-4E1C-805B-DE6397B456C9>