From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 0/2] ARM: dts: aspeed: Fix SCU IRQ controller node addresses
Date: Tue, 4 Feb 2020 16:49:06 -0600 [thread overview]
Message-ID: <20200204224908.19967-1-eajames@linux.ibm.com> (raw)
Warnings were introduced due to unit address on nodes that had no reg property.
Drop the unit addresses from the nodes.
Eddie James (2):
ARM: dts: aspeed: ast2500: Fix SCU IRQ controller node address
ARM: dts: aspeed: ast2600: Fix SCU IRQ controller node addresses
arch/arm/boot/dts/aspeed-g5.dtsi | 2 +-
arch/arm/boot/dts/aspeed-g6.dtsi | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.24.0
next reply other threads:[~2020-02-04 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 22:49 Eddie James [this message]
2020-02-04 22:49 ` [PATCH 1/2] ARM: dts: aspeed: ast2500: Fix SCU IRQ controller node address Eddie James
2020-02-10 2:28 ` Joel Stanley
2020-02-04 22:49 ` [PATCH 2/2] ARM: dts: aspeed: ast2600: Fix SCU IRQ controller node addresses Eddie James
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=20200204224908.19967-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=linux-aspeed@lists.ozlabs.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).