From: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [PATCH 0/2] ARM: dts: bcm283x: Fix DTC warnings
Date: Sat, 24 Feb 2018 15:15:20 +0100 [thread overview]
Message-ID: <1519481722-22738-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series fixes some DTC warnings, which are only visible with W=1.
Stefan Wahren (2):
ARM: dts: bcm283x: Fix unit address of local_intc
ARM: dts: bcm283x: Move arm-pmu out of soc node
arch/arm/boot/dts/bcm2835.dtsi | 6 +++---
arch/arm/boot/dts/bcm2836.dtsi | 12 ++++++------
arch/arm/boot/dts/bcm2837.dtsi | 2 +-
3 files changed, 10 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2018-02-24 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 14:15 Stefan Wahren [this message]
[not found] ` <1519481722-22738-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2018-02-24 14:15 ` [PATCH 1/2] ARM: dts: bcm283x: Fix unit address of local_intc Stefan Wahren
2018-02-24 14:15 ` [PATCH 2/2] ARM: dts: bcm283x: Move arm-pmu out of soc node Stefan Wahren
[not found] ` <1519481722-22738-3-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2018-02-26 18:26 ` Eric Anholt
[not found] ` <87fu5nppxo.fsf-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2018-02-26 19:09 ` Stefan Wahren
[not found] ` <216513579.120636.1519672190175-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2018-02-26 23:32 ` Eric Anholt
2018-02-28 0:42 ` [PATCH 0/2] ARM: dts: bcm283x: Fix DTC warnings Florian Fainelli
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=1519481722-22738-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren-es4nqchxeme@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).