linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"arm@kernel.org" <arm@kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the gpio tree
Date: Thu, 16 Nov 2017 09:42:44 +1100	[thread overview]
Message-ID: <20171116094244.55db9408@canb.auug.org.au> (raw)
In-Reply-To: <CABGGisyhjtJN=Rgjb0MS9vg+TH2M8Rir27GNyv8jAT2LibjASg@mail.gmail.com>

Hi all,

On Thu, 9 Nov 2017 08:37:00 -0600 Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> >> On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> >>>
> >>> After merging the gpio tree, yesterday's linux-next build (arm
> >>> multi_v7_defconfig) produced these warnings:
> >>>
> >>> arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-b-rev2.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-a.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-b-plus.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-a-plus.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2836-rpi-2-b.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2837-rpi-3-b.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-zero.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/bcm2835-rpi-zero-w.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e980000:phys[0])
> >>> arch/arm/boot/dts/exynos5410-odroidxu.dtb: Warning (interrupts_property): Missing interrupt-controller or interrupt-map property in /soc/system-controller@10040000
> >>>
> >>> and many, many more.
> >>>
> >>> I have no idea what caused this.  
> >>
> >> I am still getting lots of these ...  
> >
> > I have absolutely no clue either.
> >
> > What I know is that there is a device tree compiler warning that can
> > be turned on, and
> > it generates these warnings a lot. The actual problems have been in
> > the DTS files
> > forever. They just recently started to look into them.
> >
> > It has nothing to do with the GPIO tree whatsoever, so I wonder if it
> > is a side effect of
> > something else?  

Probably just the first tree to cause a rebuild of the dtb files after
the change below.

> There's a dtc update in -next which adds these new checks. It's been
> there for over a month now. Unlike other dtc checks, these are
> generally actual errors, so they are not off by default (enabled with
> W=1,2).
> 
> In reality, there's only about 50-100 warnings. The way dts includes
> are structured and because the dtc checks don't have the original
> source file lines, it just multiplies the warnings.

So these (many) warnings are now in Linus' tree :-(

Please do something about them.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-11-15 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03  5:37 linux-next: build warnings after merge of the gpio tree Stephen Rothwell
2017-11-09  3:51 ` Stephen Rothwell
2017-11-09  7:42   ` Linus Walleij
2017-11-09 14:37     ` Rob Herring
2017-11-15 22:42       ` Stephen Rothwell [this message]
2017-11-15 23:12         ` Rob Herring
2017-11-15 23:39           ` Stephen Rothwell
2017-12-05 22:48           ` Stephen Rothwell
2017-12-06 20:51             ` Rob Herring
2017-12-07 15:10               ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2014-07-23  8:45 Stephen Rothwell
2014-07-23  8:46 ` Linus Walleij

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=20171116094244.55db9408@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arm@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@kernel.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).