From: Rob Herring <robh@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
David Daney <david.daney@cavium.com>,
Linus Walleij <linus.walleij@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>
Subject: Re: next/master build: 214 builds: 26 failed, 188 passed, 28 errors, 6333 warnings (next-20171107)
Date: Tue, 7 Nov 2017 08:02:47 -0600 [thread overview]
Message-ID: <CAL_JsqJsXzgUvQrBXGQxuOrb-QUjOOiSyqhpF-V9NeaKG4TyrA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3QKkGv6eSjX7wH6LpOY0-1XUPFoX0ntog5-ZSHPab6iA@mail.gmail.com>
On Tue, Nov 7, 2017 at 6:15 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tue, Nov 7, 2017 at 7:59 AM, kernelci.org bot <bot@kernelci.org> wrote:
>> 12 arch/arm/boot/dts/spear1340-evb.dtb: Warning (dmas_property): Property 'dmas', cell 4 is not a phandle reference in /ahb/apb/serial@b4100000
>> 12 arch/arm/boot/dts/spear1340-evb.dtb: Warning (dmas_property): Missing property '#dma-cells' in node /interrupt-controller@ec801000 or bad phandle (referred from /ahb/apb/serial@b4100000:dmas[4])
>> 12 arch/arm/boot/dts/spear1310-evb.dtb: Warning (gpios_property): Property 'cs-gpios', cell 6 is not a phandle reference in /ahb/apb/spi@e0100000
>> 12 arch/arm/boot/dts/spear1310-evb.dtb: Warning (gpios_property): Missing property '#gpio-cells' in node /interrupt-controller@ec801000 or bad phandle (referred from /ahb/apb/spi@e0100000:cs-gpios[6])
> ...
>
> endless stream of new dtc warnings, mostly valid. I have started
> fixing them but at some point
> gave up. Looking for help here.
Sorry, I intended to have these show up early in the cycle to give
time to fix, but between -next being sporadic and kernelci needing a
change to report dtc warnings it all landed late. It's really only
50-100 unique errors. Things just explode since everything is an
include file.
Rob
next prev parent reply other threads:[~2017-11-07 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a0159b6.08bc500a.ebe4b.25c6@mx.google.com>
[not found] ` <5a0159b6.08bc500a.ebe4b.25c6-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2017-11-07 12:15 ` next/master build: 214 builds: 26 failed, 188 passed, 28 errors, 6333 warnings (next-20171107) Arnd Bergmann
2017-11-07 14:02 ` Rob Herring [this message]
2017-11-07 15:21 ` Linus Walleij
[not found] ` <CACRpkdZLggJA_qcRSJv4tndHDU4SG6HhP1U8uJpiKn=gBpAneA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-07 16:06 ` Arnd Bergmann
[not found] ` <CAK8P3a3QKkGv6eSjX7wH6LpOY0-1XUPFoX0ntog5-ZSHPab6iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-07 17:52 ` David Daney
2017-11-07 18:17 ` James Hogan
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=CAL_JsqJsXzgUvQrBXGQxuOrb-QUjOOiSyqhpF-V9NeaKG4TyrA@mail.gmail.com \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mhiramat@kernel.org \
--cc=ralf@linux-mips.org \
/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).