From: xuwei5@hisilicon•com (Wei Xu)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm64: dts: hip06: Fix no reg property warning
Date: Tue, 15 Nov 2016 16:13:40 +0000 [thread overview]
Message-ID: <582B3434.5090604@hisilicon.com> (raw)
In-Reply-To: <1477280428-30558-1-git-send-email-wangkefeng.wang@huawei.com>
Hi Kefeng,
On 2016/10/24 4:40, Kefeng Wang wrote:
> Warning (unit_address_vs_reg): Node /soc/ethernet at 4 has a unit name, but no reg property
> Warning (unit_address_vs_reg): Node /soc/ethernet at 5 has a unit name, but no reg property
> Warning (unit_address_vs_reg): Node /soc/ethernet at 0 has a unit name, but no reg property
> Warning (unit_address_vs_reg): Node /soc/ethernet at 1 has a unit name, but no reg property
>
> Fix warning when build with W=1.
>
> Cc: Kejian Yan <yankejian@huawei•com>
> Cc: Yisen Zhuang <yisen.zhuang@huawei•com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei•com>
> ---
Applied to the hisilicon soc tree.
Thanks!
Best Regards,
Wei
> arch/arm64/boot/dts/hisilicon/hip06.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hip06.dtsi b/arch/arm64/boot/dts/hisilicon/hip06.dtsi
> index b548763..f66c51b 100644
> --- a/arch/arm64/boot/dts/hisilicon/hip06.dtsi
> +++ b/arch/arm64/boot/dts/hisilicon/hip06.dtsi
> @@ -508,7 +508,7 @@
> };
> };
>
> - eth0: ethernet at 4{
> + eth0: ethernet-4{
> compatible = "hisilicon,hns-nic-v2";
> ae-handle = <&dsaf0>;
> port-idx-in-ae = <4>;
> @@ -517,7 +517,7 @@
> dma-coherent;
> };
>
> - eth1: ethernet at 5{
> + eth1: ethernet-5{
> compatible = "hisilicon,hns-nic-v2";
> ae-handle = <&dsaf0>;
> port-idx-in-ae = <5>;
> @@ -526,7 +526,7 @@
> dma-coherent;
> };
>
> - eth2: ethernet at 0{
> + eth2: ethernet-0{
> compatible = "hisilicon,hns-nic-v2";
> ae-handle = <&dsaf0>;
> port-idx-in-ae = <0>;
> @@ -535,7 +535,7 @@
> dma-coherent;
> };
>
> - eth3: ethernet at 1{
> + eth3: ethernet-1{
> compatible = "hisilicon,hns-nic-v2";
> ae-handle = <&dsaf0>;
> port-idx-in-ae = <1>;
>
next prev parent reply other threads:[~2016-11-15 16:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 9:14 [PATCH 0/5] arm64: dts: hisilicon: Hip06 fix and support Hip07 D05 board Kefeng Wang
2016-09-24 9:14 ` [PATCH 1/5] arm64: dts: hip06: Correct hardware pin number of usb node Kefeng Wang
2016-10-24 3:40 ` [PATCH] arm64: dts: hip06: Fix no reg property warning Kefeng Wang
2016-11-15 16:13 ` Wei Xu [this message]
2016-11-15 16:17 ` [PATCH 1/5] arm64: dts: hip06: Correct hardware pin number of usb node Wei Xu
2016-09-24 9:14 ` [PATCH 2/5] Documentation: arm64: Add Hisilicon Hip07 D05 dts binding Kefeng Wang
2016-11-15 16:17 ` Wei Xu
2016-09-24 9:14 ` [PATCH 3/5] arm64: dts: hisilicon: Add initial dts for Hip07 D05 board Kefeng Wang
2016-11-15 16:18 ` Wei Xu
2016-09-24 9:14 ` [PATCH 4/5] tty: amba-pl011: Don't complain on -EPROBE_DEFER when no irq Kefeng Wang
2016-09-24 9:14 ` [PATCH 5/5] tty: amba-pl011: Add earlycon support for SBSA UART Kefeng Wang
2016-09-27 10:57 ` Greg Kroah-Hartman
2016-09-27 13:15 ` Kefeng Wang
2016-10-24 3:59 ` Kefeng Wang
2016-10-27 15:18 ` Greg Kroah-Hartman
2016-10-30 8:49 ` Kefeng Wang
2016-10-30 13:31 ` Greg Kroah-Hartman
2016-10-31 2:04 ` [PATCH RESEND] " Kefeng Wang
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=582B3434.5090604@hisilicon.com \
--to=xuwei5@hisilicon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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