From: danielwa@cisco.com (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-RFC 5/7] arm: convert to generic builtin command line
Date: Tue, 20 Oct 2015 12:54:52 -0700 [thread overview]
Message-ID: <56269C0C.3030400@cisco.com> (raw)
In-Reply-To: <CAL_Jsq+qF5DNqQYyL2pAeCX=+1xb6p7bY2SUoi4Mm1YrMtQTLA@mail.gmail.com>
On 10/07/2015 02:48 PM, Rob Herring wrote:
>> #ifndef MEM_SIZE
>> > #define MEM_SIZE (16*1024*1024)
>> >@@ -125,16 +126,9 @@ __tagtable(ATAG_REVISION, parse_tag_revision);
>> >
>> > static int __init parse_tag_cmdline(const struct tag *tag)
>> > {
>> >-#if defined(CONFIG_CMDLINE_EXTEND)
>> >- strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
>> > strlcat(default_command_line, tag->u.cmdline.cmdline,
>> > COMMAND_LINE_SIZE);
> Just do this here:
>
> cmdline_add_builtin(boot_command_line, tag->u.cmdline.cmdline,
> COMMAND_LINE_SIZE);
>
> and remove everything from setup_machine_tags.
>
> Also, I don't think there is any reason to have cmd_line and copy
> boot_command_line to it in setup.c.
>
I don't think this function runs if there's no cmdline atag, so if the
code is here then without a atag for cmdline you wouldn't get the
builtin command line either which I don't think make sense. We should
get the builtin regardless of this atag appearing, or if there's a DT
bootargs.
Daniel
prev parent reply other threads:[~2015-10-20 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 15:47 [PATCH-RFC 5/7] arm: convert to generic builtin command line Daniel Walker
2015-10-06 16:00 ` Russell King - ARM Linux
2015-10-07 21:48 ` Rob Herring
2015-10-20 19:54 ` Daniel Walker [this message]
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=56269C0C.3030400@cisco.com \
--to=danielwa@cisco.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).