From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [PATCH 2/8] introduce the device async action mechanism Date: Thu, 16 Jul 2009 21:31:06 -0700 Message-ID: <20090716213106.32d61d53@infradead.org> References: <1247643516.26272.77.camel@rzhang-dt> <20090715060006.71c2e2b6@infradead.org> <1247709910.26272.159.camel@rzhang-dt> <200907170312.00006.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200907170312.00006.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Zhang Rui , Linux Kernel Mailing List , linux-pm , linux-acpi , Len Brown , Pavel Machek , "Van De Ven, Arjan" List-Id: linux-acpi@vger.kernel.org On Fri, 17 Jul 2009 03:11:59 +0200 "Rafael J. Wysocki" wrote: > > Well, first, I'm not really sure that using the async _boot_ > infrastructure for that is a good choice. the async function call mechanism is for more than boot. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org