From: Lucas Stach <l.stach@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: Thu, 12 Dec 2019 10:45:34 +0100 [thread overview]
Message-ID: <7e13626ae46b6241549e33c983695bed316e9a6f.camel@pengutronix.de> (raw)
In-Reply-To: <20191212013323.GZ15858@dragon>
Hi Shawn,
On Do, 2019-12-12 at 09:33 +0800, Shawn Guo wrote:
> Hi Stephen,
>
> On Thu, Dec 12, 2019 at 08:35:56AM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
>
> Sorry for the breakage.
>
[...]
> > The warning was (probably) introduced by commit
> >
> > e79295edf1df ("ARM: dts: imx6: RDU2: link eDP bridge to panel")
>
> I have just taken these two commits out.
The commit message of this change should maybe have been clearer, but
the warning is expected. The bootloader fixes the DT before passing it
on to Linux by completing the other direction of link if eDP is
enabled.
How do we want to handle this? If you totally dislike the warning I can
get around it by not adding the link and adding some more complexity to
the bootloader, but given the choice I would like to keep the
incomplete link in the Linux DT and keep bootloader complexity down.
Regards,
Lucas
next prev parent reply other threads:[~2019-12-12 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 21:35 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2019-12-12 1:33 ` Shawn Guo
2019-12-12 9:45 ` Lucas Stach [this message]
2019-12-12 11:37 ` Shawn Guo
-- 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-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
2019-01-10 22:30 Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15 ` Lukasz Majewski
2019-01-12 1:23 ` 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=7e13626ae46b6241549e33c983695bed316e9a6f.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawnguo@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).