From: Shawn Guo <shawn.guo@linaro.org>
To: Lukasz Majewski <lukma@denx.de>
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>
Subject: Re: linux-next: build failure after merge of the imx-mxs tree
Date: Sat, 12 Jan 2019 09:23:26 +0800 [thread overview]
Message-ID: <20190112012323.GA8478@dragon> (raw)
In-Reply-To: <20190111001559.12d91530@jawa>
On Fri, Jan 11, 2019 at 12:15:59AM +0100, Lukasz Majewski wrote:
> Hi Stephen,
>
> > Hi all,
> >
> > On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
> > <sfr@canb.auug.org.au> wrote:
> > >
> > > After merging the imx-mxs tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:
> >
> > Actually this is only treated as a warning.
Thanks for reporting, Stephen.
>
> Thanks for the notification. I will look on that (soon).
I just sent a fix for it.
https://patchwork.kernel.org/patch/10760827/
>
> >
> > > arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning
> > > (spi_bus_bridge): /soc/aips-bus@40080000/spi@400ad000: incorrect
> > > #address-cells for SPI bus also defined at
> > > arch/arm/boot/dts/vf610-bk4.dts:130.8-142.3
> > > arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> > > prerequisite 'spi_bus_bridge'
> > >
> > >
> > > Caused by commit
> > >
> > > cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading
> > > ID code from MVB device")
I found that the warning exists even on v5.0-rc1, so it's not caused by
Lukasz's change.
Shawn
next prev parent reply other threads:[~2019-01-12 1:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 22:30 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15 ` Lukasz Majewski
2019-01-12 1:23 ` Shawn Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-07 1:31 Stephen Rothwell
2022-10-30 22:09 Stephen Rothwell
2022-10-30 22:11 ` Alistair
2022-10-31 0:52 ` Shawn Guo
2021-12-06 22:10 Stephen Rothwell
2021-12-07 7:27 ` Michal Vokáč
2020-11-03 1:00 Stephen Rothwell
2020-11-03 6:39 ` Shawn Guo
2020-02-18 2:08 Stephen Rothwell
2020-02-18 2:18 ` Peng Fan
2020-02-18 9:38 ` Shawn Guo
2019-12-11 21:35 Stephen Rothwell
2019-12-12 1:33 ` Shawn Guo
2019-12-12 9:45 ` Lucas Stach
2019-12-12 11:37 ` Shawn Guo
2019-05-20 22:37 Stephen Rothwell
2019-05-21 2:16 ` Anson Huang
2019-05-21 4:43 ` Shawn Guo
2019-04-22 22:45 Stephen Rothwell
2019-04-22 22:54 ` Fabio Estevam
2019-04-23 2:12 ` Shawn Guo
2015-06-01 12:35 Stephen Rothwell
2015-05-29 11:28 Stephen Rothwell
2015-05-29 13:16 ` 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=20190112012323.GA8478@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukma@denx.de \
--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).