From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: dts: introduce MPS2 AN385/AN386
Date: Mon, 25 Apr 2016 13:32:39 +0200 [thread overview]
Message-ID: <5670114.66Ur0mq4Xc@wuerfel> (raw)
In-Reply-To: <571DEE47.3090208@arm.com>
On Monday 25 April 2016 11:15:35 Vladimir Murzin wrote:
> >> +
> >> +#include "mps2.dtsi"
> >> +
> >> +/ {
> >> + model = "ARM MPS2 Application Note 385/386";
> >> + compatible = "arm,mps2";
> >> +
> >> + aliases {
> >> + serial0 = &uart0;
> >> + };
> >> +
> >> + chosen {
> >> + bootargs = "rdinit=/sbin/init earlycon";
> >
> > The rootfs should be independent from the board.
> > In my opinion, this type of bootargs should not be part of the DTS.
>
> I have no strong opinion on this, but quick grep shows plenty places
> where the same happens, and even [1] has rootfs specific option as an
> example. So if there is no strong call to remove rdinit from bootargs,
> I'd prefer to keep it as it makes testing easier for me.
>
> [1] Documentation/devicetree/booting-without-of.txt
>
I think "rdinit=/sbin/init" is redundant, that is what we try running
anyway, so I don't see any downside in removing it.
Arnd
next prev parent reply other threads:[~2016-04-25 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 8:49 [PATCH 0/5] Support MPS2 platform Vladimir Murzin
2016-04-25 8:49 ` [PATCH 1/5] ARM: vexpress/mps2: introduce " Vladimir Murzin
2016-04-25 8:49 ` [PATCH 2/5] ARM: configs: add MPS2 defconfig Vladimir Murzin
2016-04-25 8:49 ` [PATCH 3/5] ARM: dts: introduce MPS2 AN385/AN386 Vladimir Murzin
2016-04-25 9:23 ` Matthias Brugger
2016-04-25 10:15 ` Vladimir Murzin
2016-04-25 11:32 ` Arnd Bergmann [this message]
2016-04-25 12:03 ` Vladimir Murzin
2016-04-25 13:52 ` Sudeep Holla
2016-04-25 8:49 ` [PATCH 4/5] ARM: dts: introduce MPS2 AN399/AN400 Vladimir Murzin
2016-04-25 9:24 ` Matthias Brugger
2016-04-25 8:49 ` [PATCH 5/5] MAINTAINERS: Update ARM Versatile Express platform entry Vladimir Murzin
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=5670114.66Ur0mq4Xc@wuerfel \
--to=arnd@arndb.de \
--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