From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
linux kernel <linux-kernel@vger.kernel.org>,
linux-embedded <linux-embedded@vger.kernel.org>,
Matt Mackall <mpm@selenic.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] bootup: Add built-in kernel command line for x86
Date: Wed, 06 Aug 2008 16:03:41 -0700 [thread overview]
Message-ID: <489A2DCD.8020804@zytor.com> (raw)
In-Reply-To: <489A2D0F.2070102@am.sony.com>
Tim Bird wrote:
>
>> CONFIG_CMDLINE_OVERRIDE is probably more palatable to other architectures.
>
> I'd be OK implementing it with an option, rather than a magic char.
> I was trying to avoid adding too many options, since many kernel
> developers prefer fewer options where possible. But the magic
> char makes the code less straightforward.
>
> If we ever move towards supporting both prefix and suffice splicing (or
> even complicated in-the-middle splicing), then the magic char is
> easier to develop into that. But so far, I can only come up with
> reasonable cases for append and override, and I don't want to add
> superfluous handling for non-existent use cases.
I think I agree, and the override option would make it easier to make
generic.
-hpa
next prev parent reply other threads:[~2008-08-06 23:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 21:31 [PATCH] bootup: Add built-in kernel command line for x86 Tim Bird
2008-08-06 21:31 ` Tim Bird
2008-08-06 22:04 ` Robert Schwebel
2008-08-06 22:22 ` Tim Bird
2008-08-06 22:48 ` H. Peter Anvin
2008-08-06 22:52 ` Matt Mackall
2008-08-06 23:02 ` H. Peter Anvin
2008-08-06 23:00 ` Tim Bird
2008-08-06 23:03 ` H. Peter Anvin [this message]
2008-08-06 22:14 ` Matt Mackall
2008-08-06 22:31 ` Tim Bird
2008-08-06 22:48 ` Matt Mackall
2008-08-11 19:10 ` Ingo Molnar
2008-08-11 19:23 ` H. Peter Anvin
2008-08-11 22:40 ` Tim Bird
2008-08-12 19:52 ` [PATCH] bootup: Add built-in kernel command line for x86 (v2) Tim Bird
2008-08-15 14:03 ` Ingo Molnar
2008-08-15 14:12 ` Ingo Molnar
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=489A2DCD.8020804@zytor.com \
--to=hpa@zytor.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=r.schwebel@pengutronix.de \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.