linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: linux-next: build warning after merge of the imx-mxs tree
Date: Mon, 14 May 2018 21:42:02 +0800	[thread overview]
Message-ID: <20180514134200.GB11867@dragon> (raw)
In-Reply-To: <CAL_JsqJDj3Gx__L7Dc2WSEQ+MnJp-e2aO4K498qq5odkco-dCQ@mail.gmail.com>

On Mon, May 14, 2018 at 08:05:29AM -0500, Rob Herring wrote:
> On Sun, May 13, 2018 at 7:56 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > Hi Stephen,
> >
> > On Mon, May 14, 2018 at 09:21:58AM +1000, Stephen Rothwell wrote:
> >> Hi Shawn,
> >>
> >> After merging the imx-mxs tree, today's linux-next build (arm
> >> multi_v7_defconfig) produced this warning:
> >>
> >> arch/arm/boot/dts/imx6dl-aristainetos_7.dtb: Warning (reg_format): /soc/ipu@2400000/port@2/endpoint@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
> >> arch/arm/boot/dts/imx6dl-aristainetos_7.dtb: Warning (pci_device_bus_num): Failed prerequisite 'reg_format'
> >> arch/arm/boot/dts/imx6dl-aristainetos_7.dtb: Warning (simple_bus_reg): Failed prerequisite 'reg_format'
> >> arch/arm/boot/dts/imx6dl-aristainetos_7.dtb: Warning (avoid_default_addr_size): /soc/ipu@2400000/port@2/endpoint@0: Relying on default #address-cells value
> >>
> >> and about 7000 more lines across several files ...
> >>
> >> It is hard tell what introduced these warnings ...
> >
> > Commit e6bb17850d1e ("ARM: dts: imx: fix IPU OF graph endpoint node
> > names") introduced the warnings.  I will submit a patch to fix them.
> > Sorry for this.
> 
> Well, it was the combination of that and commit ed94e3c3ceb4 ("ARM:
> dts: imx6: Remove #address/#size-cells from ipu nodes"). Commit
> ed94e3c3ceb4q should be reverted.

Ah, okay.  I will just drop that commit then.

Shawn

  reply	other threads:[~2018-05-14 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 23:21 linux-next: build warning after merge of the imx-mxs tree Stephen Rothwell
2018-05-14  0:56 ` Shawn Guo
2018-05-14 13:05   ` Rob Herring
2018-05-14 13:42     ` Shawn Guo [this message]
2022-04-26  0:06 Stephen Rothwell
2022-04-26  1:15 ` Shawn Guo

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=20180514134200.GB11867@dragon \
    --to=shawn.guo@linaro.org \
    --cc=fabio.estevam@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@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).