linux-kernel - Re: linux-next: build failure after merge of the usb 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]

Message-ID: <20220614175247.30b02dc2@canb.auug.org.au>
Date:   Tue, 14 Jun 2022 17:52:47 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greg KH <greg@...ah.com>
Cc:     Neal Liu <neal_liu@...eedtech.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the usb tree

Hi Greg,

On Tue, 14 Jun 2022 08:41:53 +0200 Greg KH <greg@...ah.com> wrote:
>
> On Tue, Jun 14, 2022 at 12:08:33PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the usb tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> 
> Failed like what?

Sorry about that.  I no longer have the actual error message, but it
was complaining about a duplicate DT node "ahb usb@...a2000".  The
patch managed to be applied twice.

> > Caused by commit
> > 
> >   2cee50bf4590 ("ARM: dts: aspeed: Add USB2.0 device controller node")
> > 
> > I have used the usb tree from next-20220610 for today.  
> 
> Odd, ok, I'll try to revert the offending dts change from my tree.  If I
> can get a hint as to what went wrong with the build, that would also be
> great :)

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped