Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755947AbZLICyw (ORCPT ); Tue, 8 Dec 2009 21:54:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755563AbZLICyv (ORCPT ); Tue, 8 Dec 2009 21:54:51 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:45464 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755521AbZLICyv (ORCPT ); Tue, 8 Dec 2009 21:54:51 -0500 Date: Tue, 8 Dec 2009 18:54:43 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Alan Stern cc: "Rafael J. Wysocki" , Zhang Rui , LKML , ACPI Devel Maling List , pm list Subject: Re: Async resume patch (was: Re: [GIT PULL] PM updates for 2.6.33) In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 767 Lines: 20 On Tue, 8 Dec 2009, Alan Stern wrote: > > You mean, if A comes before B in the list and A must suspend after B? But if they are not topologically ordered, then A wouldn't necessarily be before B on the list in the first place. Of course, if we've mucked with the list by hand and made sure the ordering is ok, then that's a different issue. But your whole point seemed to be that the device could impose its own ordering in its suspend callback, which is not true on its own without external ordering. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/