public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: [PATCH] Handle disabled local apic better
Date: 24 Mar 2004 15:48:46 -0500	[thread overview]
Message-ID: <1080161325.18504.268.camel@dhcppc4> (raw)
In-Reply-To: <20040324192800.GD20849-B4tOwbsTzaBolqkO4TVVkw@public.gmane.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

  parent reply	other threads:[~2004-03-24 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 20:35 [PATCH] Handle disabled local apic better Andi Kleen
     [not found] ` <20040323213551.4789bbae.ak-l3A5Bk7waGM@public.gmane.org>
2004-03-24  7:12   ` Len Brown
     [not found]     ` <1080112373.18504.67.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-24  4:27       ` Andi Kleen
     [not found]         ` <20040324052724.56e57709.ak-l3A5Bk7waGM@public.gmane.org>
2004-03-24 19:13           ` Len Brown
     [not found]             ` <1080155600.18509.263.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-24 19:28               ` Andi Kleen
     [not found]                 ` <20040324192800.GD20849-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-24 20:48                   ` Len Brown [this message]
2004-03-24  8:03       ` Karol Kozimor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1080161325.18504.268.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ak-l3A5Bk7waGM@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox