From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: oskar.andero@sonyericsson.com, nicolas.pitre@linaro.org,
linux@arm.linux.org.uk, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
eric.y.miao@gmail.com, linux-arm-kernel@lists.infradead.org,
Victor Boivie <victor.boivie@sonyericsson.com>
Subject: Re: [PATCH] ARM: Allow for kernel command line concatenation
Date: Thu, 7 Apr 2011 12:58:50 +0200 [thread overview]
Message-ID: <20110407105850.GJ13963@pengutronix.de> (raw)
In-Reply-To: <1302172525.24493.7.camel@t41.thuisdomein>
On Thu, Apr 07, 2011 at 12:35:01PM +0200, Paul Bolle wrote:
> On Thu, 2011-04-07 at 10:17 +0200, oskar.andero@sonyericsson.com wrote:
> > +config CMDLINE_EXTEND
> > + bool "Extend bootloader kernel arguments"
> > + depends on CMDLINE != ""
> > + help
> > + The default kernel command string will be concatenated with the
> > + arguments provided by the boot loader.
>
> This suggests the parameters provided by the boot loader will override
> corresponding parameters of the default kernel command string. Is that
> correct (for all possible parameters)?
>
> Either way, shouldn't it be documented, perhaps in this help text, what
> will happen if a parameter of the default kernel command string and a
> parameter provided by the boot loader somehow conflict?
Then you will end up with both parameters I guess. What happens depends
on the parameter in question I guess. IMHO the description is fine.
But I wonder if the new mechanism is useful in the end.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-04-07 10:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 8:17 [PATCH] ARM: Allow for kernel command line concatenation oskar.andero
2011-04-07 9:01 ` Uwe Kleine-König
2011-04-07 10:35 ` Paul Bolle
2011-04-07 10:58 ` Uwe Kleine-König [this message]
2011-04-07 11:38 ` Boivie, Victor
2011-04-07 13:18 ` Nick Bowler
2011-04-07 13:22 ` Boivie, Victor
2011-04-07 11:47 oskar.andero
2011-04-07 13:29 oskar.andero
2011-04-07 18:50 ` Nicolas Pitre
2011-04-07 19:15 ` Uwe Kleine-König
2011-04-08 9:36 oskar.andero
2011-05-04 15:03 ` oskar.andero
2011-05-04 15:11 ` Uwe Kleine-König
2011-05-04 16:10 ` oskar.andero
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=20110407105850.GJ13963@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=catalin.marinas@arm.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=oskar.andero@sonyericsson.com \
--cc=pebolle@tiscali.nl \
--cc=victor.boivie@sonyericsson.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).