From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Brian Norris" <computersforpeace@gmail.com>,
"Gregory Fong" <gregory.0xf0@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] ARM: dts: Fix BCM7445 DTC warnings
Date: Tue, 11 Jun 2019 14:53:48 -0700 [thread overview]
Message-ID: <20190611215348.9994-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20190528230134.27007-2-f.fainelli@gmail.com>
On Tue, 28 May 2019 16:01:28 -0700, Florian Fainelli <f.fainelli@gmail.com> wrote:
> Fixes a number of unit_address_vs_reg warnings:
>
> DTC arch/arm/boot/dts/bcm7445-bcm97445svmb.dtb
> arch/arm/boot/dts/bcm7445.dtsi:66.6-225.4: Warning (unit_address_vs_reg): /rdb: node has a reg or ranges property, but no unit name
> arch/arm/boot/dts/bcm7445.dtsi:227.21-298.4: Warning (unit_address_vs_reg): /memory_controllers: node has a reg or ranges property, but no unit name
> arch/arm/boot/dts/bcm7445-bcm97445svmb.dts:9.9-14.4: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name
> arch/arm/boot/dts/bcm7445.dtsi:255.10-275.5: Warning (simple_bus_reg): /memory_controllers/memc@1: simple-bus unit address format error, expected "80000"
> arch/arm/boot/dts/bcm7445.dtsi:277.10-297.5: Warning (simple_bus_reg): /memory_controllers/memc@2: simple-bus unit address format error, expected "100000"
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
Applied to devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2019-06-11 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 23:01 [PATCH 0/7] ARM: dts: Broadcom: Fix W=1 DTC warnings Florian Fainelli
2019-05-28 23:01 ` [PATCH 1/7] ARM: dts: Fix BCM7445 " Florian Fainelli
2019-06-11 21:53 ` Florian Fainelli [this message]
2019-05-28 23:01 ` [PATCH 2/7] ARM: dts: Cygnus: Fix most DTC W=1 warnings Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 3/7] ARM: dts: bcm-mobile: " Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 4/7] ARM: dts: BCM53573: Fix " Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 5/7] ARM: dts: BCM63xx: " Florian Fainelli
2019-06-11 21:56 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 6/7] ARM: dts: BCM5301X: Fix most " Florian Fainelli
2019-06-11 22:08 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 7/7] ARM: dts: NSP: Fix the bulk of W=1 DTC warnings Florian Fainelli
2019-06-11 21:58 ` Florian Fainelli
2019-05-30 10:12 ` [PATCH 0/7] ARM: dts: Broadcom: Fix " Stefan Wahren
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=20190611215348.9994-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.0xf0@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--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 NNTP newsgroup(s).