From: Anatolij Gustschin <agust@denx.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: build warnings in Linus' tree
Date: Thu, 14 Oct 2021 00:28:41 +0200 [thread overview]
Message-ID: <20211014002841.7c4ccf2f@crub> (raw)
In-Reply-To: <CAL_JsqJSqqYya-xe8YQs0-0KTF3LzwkyGD_2dUxQY9SKVV7RMw@mail.gmail.com>
On Wed, 13 Oct 2021 17:17:25 -0500
Rob Herring robh+dt@kernel.org wrote:
...
>In general, you shouldn't need to be changing the drivers. Can you
>tell me which warnings need driver changes?
ethernet and mdio drivers share registers, so they use same unit-address:
arch/powerpc/boot/dts/tqm5200.dts:127.17-133.5: Warning (unique_unit_address): /soc5200@f0000000/ethernet@3000: duplicate unit-address (also used in node /soc5200@f0000000/mdio@3000)
arch/powerpc/boot/dts/mpc5200b.dtsi:218.23-223.5: Warning (unique_unit_address): /soc5200@f0000000/ethernet@3000: duplicate unit-address (also used in node /soc5200@f0000000/mdio@3000)
also defined at arch/powerpc/boot/dts/digsy_mtc.dts:60.17-62.5
Anatolij
next prev parent reply other threads:[~2021-10-13 22:29 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 5:47 linux-next: build warnings in Linus' tree Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-11 20:42 ` Rob Herring
2021-10-12 14:39 ` Arnd Bergmann
2021-10-13 22:12 ` Anatolij Gustschin
2021-10-13 22:17 ` Rob Herring
2021-10-13 22:28 ` Anatolij Gustschin [this message]
2021-10-13 23:22 ` Rob Herring
2021-10-14 8:44 ` Arnd Bergmann
2021-10-14 12:24 ` Anatolij Gustschin
-- strict thread matches above, loose matches on Subject: below --
2022-06-14 6:57 Stephen Rothwell
2022-05-26 7:21 Stephen Rothwell
2022-01-27 4:30 Stephen Rothwell
2022-01-27 6:01 ` Christoph Hellwig
2022-01-27 16:44 ` Stephen Rothwell
2022-01-27 4:24 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23 7:04 ` Borislav Petkov
2021-11-05 5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09 0:15 ` Stephen Rothwell
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31 ` Nicolas Saenz Julienne
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2013-07-04 4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2011-08-15 1:57 Stephen Rothwell
2011-05-23 1:25 Stephen Rothwell
2011-05-23 2:31 ` Eduardo Silva
2011-01-14 0:17 Stephen Rothwell
2011-01-14 0:09 Stephen Rothwell
2011-01-14 0:17 ` Andrew Morton
2011-01-14 1:06 ` Greg KH
2010-08-17 1:24 Stephen Rothwell
2010-08-30 1:42 ` Stephen Rothwell
2010-08-30 6:08 ` Zhang Rui
2010-09-03 2:01 ` Stephen Rothwell
2010-09-03 2:36 ` Len Brown
2010-09-17 4:26 ` Stephen Rothwell
2010-09-27 13:31 ` Stephen Rothwell
2010-08-07 2:21 Stephen Rothwell
2010-08-07 8:13 ` Vikas Chaudhary
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=20211014002841.7c4ccf2f@crub \
--to=agust@denx.de \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).