From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 0/4] arm: dts: Bootargs update for older boards from Renesas
Date: Thu, 18 Apr 2019 00:11:55 +0900 [thread overview]
Message-ID: <155551391518.5261.925425188248761120.sendpatchset@octo> (raw)
arm: dts: Bootargs update for older boards from Renesas
[PATCH 1/4] arm: dts: kzm9d: Add rw parameter to bootargs
[PATCH 2/4] arm: dts: bockw: Reorder bootargs
[PATCH 3/4] arm: dts: marzen: Add rw to bootargs and use ip=dhcp
[PATCH 4/4] arm: dts: ape6evm: Reorder bootargs
These patches try to make bootargs more consistent across older boards with
32-bit ARM SoCs from Renesas. Simple reordering, adding rw parameter and in
case of Marzen we go from ip=on to ip=dhcp. I believe using the ip parameter
consistently across the boards is a good first step.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Developed on top of renesas-devel-20190410-v5.1-rc4
arch/arm/boot/dts/emev2-kzm9d.dts | 2 +-
arch/arm/boot/dts/r8a73a4-ape6evm.dts | 2 +-
arch/arm/boot/dts/r8a7778-bockw.dts | 2 +-
arch/arm/boot/dts/r8a7779-marzen.dts | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2019-04-17 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 15:11 Magnus Damm [this message]
2019-04-17 15:12 ` [PATCH 1/4] arm: dts: kzm9d: Add rw parameter to bootargs Magnus Damm
2019-04-17 15:12 ` [PATCH 2/4] arm: dts: bockw: Reorder bootargs Magnus Damm
2019-04-17 15:12 ` [PATCH 3/4] arm: dts: marzen: Add rw to bootargs and use ip=dhcp Magnus Damm
2019-04-17 15:12 ` [PATCH 4/4] arm: dts: ape6evm: Reorder bootargs Magnus Damm
2019-04-17 15:48 ` [PATCH 0/4] arm: dts: Bootargs update for older boards from Renesas Simon Horman
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=155551391518.5261.925425188248761120.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.kernel.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