From: Florian Fainelli <f.fainelli@gmail.com>
To: "Arnd Bergmann" <arnd@kernel.org>,
DTML <devicetree@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Cc: Linus Walleij <linusw@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Kevin Hilman <khilman@baylibre.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>, Shawn Guo <shawnguo@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
SoC Team <soc@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>,
Gregory Clement <gregory.clement@bootlin.com>
Subject: Re: New 'make dtbs_check W=1' warnings
Date: Thu, 8 Apr 2021 20:37:21 -0700 [thread overview]
Message-ID: <632cbdec-e477-212c-f5a8-81151915fdeb@gmail.com> (raw)
In-Reply-To: <CAK8P3a1L8rWpR5b66v6Su8-m7-scA0wZQr_g_4KnV4dnrky6ZA@mail.gmail.com>
On 4/8/2021 8:08 AM, Arnd Bergmann wrote:
> Greetings to all Arm platform maintainers,
>
> I've just gone through the DT merges I've received so far and, with a
> little help from Rob,
> managed to run 'make dtbs_check W=1' before and after, to see what
> warnings we get.
> The good news is that the number of warnings is going down, but
> unfortunately there
> is still an unmanageable amount of remaining warnings, and some new
> ones crept in.
>
> I'm still working on my tooling for this, to catch these better, but
> ideally I think we should
> try to not introduce new warnings. I think some platforms are already
> clean, and I did
> not see any new warnings for mvebu, samsung and broadcom. There were a lot of
> warnings from .dtsi files, and I probably did an incomplete job at
> deduplicating those.
There are definitively a ton of warnings for Broacom DTS files, a number
of those warnings exist because the bindings were not converted to YAML.
Rafal, do you think you could help me with taking care of the
BCM5301X/4908 warnings?
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-09 3:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 15:08 New 'make dtbs_check W=1' warnings Arnd Bergmann
2021-04-08 15:25 ` Alexandre Belloni
2021-04-08 23:59 ` Rob Herring
2021-04-08 19:25 ` Krzysztof Kozlowski
2021-04-08 22:11 ` Linus Walleij
2021-04-09 3:37 ` Florian Fainelli [this message]
2021-04-09 5:27 ` Rafał Miłecki
2021-04-12 11:32 ` Geert Uytterhoeven
2021-04-12 13:14 ` Arnd Bergmann
2021-04-12 16:01 ` Bjorn Andersson
2021-04-12 18:52 ` Arnd Bergmann
2021-04-13 2:36 ` Bjorn Andersson
2021-04-13 9:55 ` Mark Brown
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=632cbdec-e477-212c-f5a8-81151915fdeb@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregory.clement@bootlin.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nm@ti.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=tony@atomide.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).