linux-kernel - Re: linux-next: build failure after merge of the imx-mxs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 12 Dec 2019 10:45:34 +0100
From:   Lucas Stach <l.stach@...gutronix.de>
To:     Shawn Guo <shawnguo@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the imx-mxs tree

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