From: Florian Fainelli <f.fainelli@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
Date: Thu, 23 Dec 2021 10:18:32 -0800 [thread overview]
Message-ID: <684e3940-0884-4139-dd4e-a16375ec9cf6@gmail.com> (raw)
In-Reply-To: <00324e0f-7825-4ddc-a823-40a698715442@arinc9.com>
On 12/23/2021 12:50 AM, Arınç ÜNAL wrote:
> Hey Florian.
>
> I'm not sure I understand what's going wrong here. I did everything
> according to the documentation here:
> https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/net/dsa/realtek-smi.txt#L158
The problem is that there is a 'reg' property for the 'ports' node when
this node is just a "container" for additional sub-node. This is because
the example you rightfully followed to the letter was wrong to begin
with. Should be fixed with:
https://lore.kernel.org/netdev/20211223181741.3999-1-f.fainelli@gmail.com/
And you would need to make a matching change to
arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts.
Thanks!
--
Florian
next prev parent reply other threads:[~2021-12-23 18:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 21:59 linux-next: build warning after merge of the arm-soc tree Stephen Rothwell
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:58 ` Florian Fainelli
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 18:18 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-02 7:49 Stephen Rothwell
2024-07-02 11:55 ` Marek Behún
2024-07-30 10:05 ` Stephen Rothwell
2023-06-22 0:48 Stephen Rothwell
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 13:55 ` Rob Herring
2021-10-25 23:39 Stephen Rothwell
2021-10-26 6:15 ` Joel Stanley
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 6:03 ` ChiaWei Wang
2021-04-06 0:45 Stephen Rothwell
2021-04-06 6:34 ` Krzysztof Kozlowski
2019-08-15 23:25 Stephen Rothwell
2019-08-15 23:23 Stephen Rothwell
2019-04-29 23:28 Stephen Rothwell
2019-05-03 6:49 ` Linus Walleij
2019-05-03 12:57 ` Arnd Bergmann
2014-01-19 23:39 Stephen Rothwell
2012-03-19 7:39 Stephen Rothwell
2012-03-19 9:40 ` Arnd Bergmann
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=684e3940-0884-4139-dd4e-a16375ec9cf6@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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