From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 9 16:14:09 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EB91106566B; Mon, 9 Apr 2012 16:14:09 +0000 (UTC) (envelope-from nate@root.org) Received: from mail.rootlabs.com (rootlabs.com [208.72.84.106]) by mx1.freebsd.org (Postfix) with ESMTP id 154188FC19; Mon, 9 Apr 2012 16:14:09 +0000 (UTC) Received: (Postfix invoked from local network); Mon, 9 Apr 2012 16:06:16 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Nate Lawson In-Reply-To: Date: Mon, 9 Apr 2012 09:06:14 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Robert Millan X-Mailer: Apple Mail (2.1084) Cc: freebsd-acpi@freebsd.org, Steven Chamberlain Subject: Re: [PATCH] Abort powerd when no cpufreq(4) support is found X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 16:14:09 -0000 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 >