linux-kernel - Re: linux-next: build warnings after merge of the broadcom 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] [day] [month] [year] [list]

Message-ID: <20221007103008.3ad5913f@canb.auug.org.au>
Date:   Fri, 7 Oct 2022 10:30:08 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Rafał Miłecki <rafal@...ecki.pl>
Cc:     Arnd Bergmann <arnd@...db.de>, Joel Stanley <joel@....id.au>,
        Florian Fainelli <f.fainelli@...il.com>,
        Olof Johansson <olof@...om.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-next <linux-next@...r.kernel.org>,
        ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: linux-next: build warnings after merge of the broadcom tree

Hi Rafał,

On Thu, 06 Oct 2022 07:14:05 +0200 Rafał Miłecki <rafal@...ecki.pl> wrote:
>
> On 2022-10-06 02:17, Stephen Rothwell wrote:
> > On Wed, 05 Oct 2022 09:21:21 +0200 "Arnd Bergmann" <arnd@...db.de> > wrote:  
> >> >> Agreed. Alternatively, we could just remove the pcie@ nodes from  
> >> bcm5301x as a hotfix, as they are clearly not usable in the
> >> current form, and none of the three versions (5.19, Rafał's
> >> patch missing ranges, and Florian's patch with incorrect ranges)
> >> actually conform to the binding.  
> >> >> I'll tentatively apply the revert for now so I can send the pull  
> >> request tonight. If someone comes up with a better fix, I can
> >> use that instead.  
> > 
> > I applied the revert to the merge of the arm-soc tree today and *all*
> > the warnings are gone.  
> 
> As explained by Joel, there are dtc and yaml warnings.
> 
> Not "*all*" warnings are gone
> dtc warnings are gone
> yaml warnings are back
> 
> Which may be OK, just clarifying.

Ah, OK, now I see.  The build I do (arm multi_v7_defconfig) does not
produce the yaml warnings (for me anyway - maybe I have not installed
some optional build tool?), so I never saw them - all I saw was all the
new dtc warnings.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped