From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: dts: vf6: fix DTC unit warnings
Date: Mon, 18 Apr 2016 11:22:29 +0200 [thread overview]
Message-ID: <5714A755.3010005@denx.de> (raw)
In-Reply-To: <57149CC2.8050708@toradex.com>
Hello Bhuvanchandra DV,
Am 18.04.2016 um 10:37 schrieb Bhuvanchandra DV:
> On 04/18/2016 10:23 AM, Heiko Schocher wrote:
>> Hello Bhuvanchandra DV,
>>
>> Am 15.04.2016 um 16:09 schrieb Bhuvanchandra DV:
>>> On 04/15/2016 04:28 PM, Heiko Schocher wrote:
>>>> Fix following warnings for all vf6 based boards:
>>>>
>>>> Warning (unit_address_vs_reg): Node
>>>> /soc/ifc at 1530000/board-control at 3,0/mdio-mux-emi1 has a reg or
>>>> ranges property, but no unit name
>>>> Warning (unit_address_vs_reg): Node /soc/aips-bus at 40000000 has a unit
>>>> name, but no reg property
>>>> Warning (unit_address_vs_reg): Node /soc/aips-bus at 40080000 has a unit
>>>> name, but no reg property
>>>
>>> May be this fix[1] which Stefan Agner submitted lately is also
>>> applicable here.
>>>
>>> [1] https://lkml.org/lkml/2016/4/2/11
>>
>> Yes, better (as it adds the reg property). I hoped for such a comment,
>> as I cannot search for all missing reg properties!
>>
>> post a v2 soon.
>
> Sure! will submit the patch.
Worked in the changes from the post on lkml, I post a v2, thanks!
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-04-18 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:58 [U-Boot] [PATCH] arm: dts: vf6: fix DTC unit warnings Heiko Schocher
2016-04-15 14:09 ` Bhuvanchandra DV
2016-04-18 4:53 ` Heiko Schocher
2016-04-18 8:37 ` Bhuvanchandra DV
2016-04-18 9:22 ` Heiko Schocher [this message]
2016-04-18 15:31 ` Tom Rini
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=5714A755.3010005@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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