From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: robh@kernel.org
Cc: arm@kernel.org, andrew@lunn.ch, alexandre.belloni@bootlin.com,
Neil Armstrong <narmstrong@baylibre.com>,
maxime.ripard@bootlin.com, linus.walleij@linaro.org,
baruch@tkos.co.il, david.brown@linaro.org, jamie@jamieiles.com,
robert.jarzmik@free.fr, linux-stm32@st-md-mailman.stormreply.com,
alexandre.torgue@st.com, jesper.nilsson@axis.com,
f.fainelli@gmail.com, khilman@baylibre.com,
gregory.clement@bootlin.com, zajec5@gmail.com, wens@csie.org,
linux-arm-kernel@axis.com, jonmason@broadcom.com,
ludovic.desroches@microchip.com,
bcm-kernel-feedback-list@broadcom.com,
Hauke Mehrtens <hauke@hauke-m.de>,
andy.gross@linaro.org, sebastian.hesselbarth@gmail.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
jason@lakedaemon.net, antoine.tenart@bootlin.com,
rjui@broadcom.com, slemieux.tyco@gmail.com,
haojian.zhuang@gmail.com, vz@mleia.com,
linux-mediatek@lists.infradead.org, lars.persson@axis.com,
gregory.0xf0@gmail.com, matthias.bgg@gmail.com,
linux-amlogic@lists.infradead.org, linux-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, baohua@kernel.org,
linux-oxnas@groups.io, eric.y.miao@gmail.com,
sbranden@broadcom.com, shiraz.linux.kernel@gmail.com,
nicolas.ferre@microchip.com, leoyang.li@nxp.com,
mcoquelin.stm32@gmail.com, vireshk@kernel.org, carlo@caione.org,
jun.nie@linaro.org, computersforpeace@gmail.com,
shawnguo@kernel.org, tsahee@annapurnalabs.com, daniel@zonque.org
Subject: Re: [PATCH] ARM: dts: Kill off skeleton{64}.dtsi
Date: Wed, 5 Dec 2018 23:21:06 +0100 [thread overview]
Message-ID: <CAFBinCCyiOurskMNYeJaC3YHZF0CCVJg7q61Gs=wdZYAH83NCw@mail.gmail.com> (raw)
In-Reply-To: <20181130170634.9467-1-robh@kernel.org>
Hi Rob,
On Fri, Nov 30, 2018 at 6:07 PM Rob Herring <robh@kernel.org> wrote:
>
> Remove the usage of skeleton.dtsi in the remaining dts files. It was
> deprecated since commit 9c0da3cc61f1 ("ARM: dts: explicitly mark
> skeleton.dtsi as deprecated"). This will make adding a unit-address to
> memory nodes easier.
thank you for cleaning this up!
> The main tricky part to removing skeleton.dtsi is we could end up with
> no /memory node at all when a bootloader depends on one being present. I
> hacked up dtc to check for this condition.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
on Meson8b Odroid-C1:
Tested-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> arch/arm/boot/dts/meson.dtsi | 3 ++-
> arch/arm/boot/dts/meson6-atv1200.dts | 1 +
> arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
> arch/arm/boot/dts/meson8b-ec100.dts | 1 +
> arch/arm/boot/dts/meson8b-mxq.dts | 1 +
> arch/arm/boot/dts/meson8b-odroidc1.dts | 1 +
> arch/arm/boot/dts/meson8m2-mxiii-plus.dts | 1 +
for the Meson changes:
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Regards
Martin
prev parent reply other threads:[~2018-12-05 22:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:06 [PATCH] ARM: dts: Kill off skeleton{64}.dtsi Rob Herring
2018-11-30 17:21 ` Linus Walleij
2018-11-30 17:52 ` Florian Fainelli
2018-12-02 19:44 ` Matthias Brugger
2018-12-03 4:02 ` Chen-Yu Tsai
2018-12-03 5:54 ` Viresh Kumar
2018-12-03 7:50 ` Maxime Ripard
2018-12-03 8:19 ` Alexandre Belloni
2018-12-03 9:01 ` Neil Armstrong
2018-12-03 9:23 ` Antoine Tenart
2018-12-03 10:29 ` Alexandre Torgue
2018-12-03 21:56 ` Robert Jarzmik
2018-12-03 22:27 ` Vladimir Zapolskiy
2018-12-04 22:36 ` Kevin Hilman
2018-12-05 22:21 ` Martin Blumenstingl [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='CAFBinCCyiOurskMNYeJaC3YHZF0CCVJg7q61Gs=wdZYAH83NCw@mail.gmail.com' \
--to=martin.blumenstingl@googlemail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=andy.gross@linaro.org \
--cc=antoine.tenart@bootlin.com \
--cc=arm@kernel.org \
--cc=baohua@kernel.org \
--cc=baruch@tkos.co.il \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=carlo@caione.org \
--cc=computersforpeace@gmail.com \
--cc=daniel@zonque.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.y.miao@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=haojian.zhuang@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jamie@jamieiles.com \
--cc=jason@lakedaemon.net \
--cc=jesper.nilsson@axis.com \
--cc=jonmason@broadcom.com \
--cc=jun.nie@linaro.org \
--cc=khilman@baylibre.com \
--cc=lars.persson@axis.com \
--cc=leoyang.li@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-oxnas@groups.io \
--cc=linux-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=ludovic.desroches@microchip.com \
--cc=matthias.bgg@gmail.com \
--cc=maxime.ripard@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=rjui@broadcom.com \
--cc=robert.jarzmik@free.fr \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shawnguo@kernel.org \
--cc=shiraz.linux.kernel@gmail.com \
--cc=slemieux.tyco@gmail.com \
--cc=tsahee@annapurnalabs.com \
--cc=vireshk@kernel.org \
--cc=vz@mleia.com \
--cc=wens@csie.org \
--cc=zajec5@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).