Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946767AbXBIXz7 (ORCPT ); Fri, 9 Feb 2007 18:55:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946549AbXBIXzj (ORCPT ); Fri, 9 Feb 2007 18:55:39 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:2817 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1423359AbXBIXzf (ORCPT ); Fri, 9 Feb 2007 18:55:35 -0500 Date: Fri, 9 Feb 2007 23:09:29 +0000 From: Pavel Machek To: Len Brown Cc: Linus Torvalds , Andrew Morton , tony.luck@intel.com, Linux Kernel Mailing List , linux-acpi@vger.kernel.org, "Accardi, Kristen" Subject: Re: [GIT PATCH] ACPI patches for 2.6.21 Message-ID: <20070209230928.GD3949@ucw.cz> References: <200702071418.51058.lenb@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702071418.51058.lenb@kernel.org> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1787 Lines: 41 Hi! > Per your request, and the request of the distros, we've changed > how ACPICA Core releases are integrated into Linux so that each > upstream (CVS) check-in appears as a single git commit. > While this process is not yet perfect, it should be vastly better > than previous "code drops" in allowing git bisect to work, > and allowing distros to cherry-pick individual fixes. > > The "bay" driver is new (and marked EXPERIMENTAL) -- adding initial > hot-plug support for ACPI controlled drive bays such as the > IBM ultrabay or the Dell Module Bay. Could you describe userland interface it uses? /proc? Will it be usable for bays on notebooks not using acpi? > The "asus-laptop" driver is also new. Consistent with msi-laptop, > it uses ACPI in platform-specific ways, but strives to avoid > exposing ACPI-specific implementation details to the user. > asus-laptop is mutually exclusive with asus_acpi, which it will > replace over time. Not including another /proc/acpi/ibm -like nightmare, is it? > the old /proc/acpi/ interfaces with cleaner interfaces in sysfs -- > non-ACPI-specific generic ones whenever possible. This effort > is not complete, but it has been in -mm for a long time and > I believe that it is time to push it upstream to benefit > from broader exposure and testing. Does it still include completely broken alarm interface? Can't find it in changelogs, so hopefully not. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/