From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: Re: [PATCH] Handle disabled local apic better Date: 24 Mar 2004 15:48:46 -0500 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <1080161325.18504.268.camel@dhcppc4> References: <20040323213551.4789bbae.ak@suse.de> <1080112373.18504.67.camel@dhcppc4> <20040324052724.56e57709.ak@suse.de> <1080155600.18509.263.camel@dhcppc4> <20040324192800.GD20849@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040324192800.GD20849-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Andi Kleen Cc: ACPI Developers List-Id: linux-acpi@vger.kernel.org On Wed, 2004-03-24 at 14:28, Andi Kleen wrote: > > > No, even when you parse in parse_cmdline_early() you need a __setup, > > > otherwise the normal __setup parser will complain about unknown > > > options. > > > > Huh? So if I boot a kernel with an unknown parameter, say > > "len=gone_fishing", where would I expect to see the complaint -- I don't > > see it in my dmesg except where the entire commmand line is dumped out. > > That will result in a environment variable len in init's environment with > value gone_fishing and is not unknown. But nolapic doesn't have a = ah, so parse_args() extracts cmdline params with '=' and what it doesn't recognize make it to init's environment. looks like i recently added some potential environment pollution to init's environment then... thanks, -Len ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click