Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758221AbYBJHVa (ORCPT ); Sun, 10 Feb 2008 02:21:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757075AbYBJHUR (ORCPT ); Sun, 10 Feb 2008 02:20:17 -0500 Received: from verein.lst.de ([213.95.11.210]:34347 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756797AbYBJHUO (ORCPT ); Sun, 10 Feb 2008 02:20:14 -0500 Date: Sun, 10 Feb 2008 08:14:54 +0100 From: Christoph Hellwig To: dsdt@gaugusch.at, len.brown@intel.com Cc: linux-kernel@vger.kernel.org Subject: Re: acpi dsts loading and populate_rootfs Message-ID: <20080210071454.GA23428@lst.de> References: <20080210071226.GA23360@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080210071226.GA23360@lst.de> User-Agent: Mutt/1.3.28i X-Spam-Score: 0 () Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1069 Lines: 22 On Sun, Feb 10, 2008 at 08:12:26AM +0100, Christoph Hellwig wrote: > Folks, moving this call around hidden behing in completely unreviewed > acpi junk is not acceptable. > > Either populate_rootfs _is_ safe to be called earlier and then we should > do it always or it's not. Either way such a change should be posted > separately and reviewd on lkml. > > Len, can you please revert "ACPI: basic initramfs DSDT override support" > aka commit 71fc47a9adf8ee89e5c96a47222915c5485ac437 until we've sorted > this out properly? Thanks. And while we're at it the file reading thing in there is utter crap aswell. You really should be using the firmware loader which works perfectly fine if you initramfs is set up for it. So please folks, back to the drawing board, do it properly and send it out to lkml for review please. -- 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/