linux-kernel - Re: linux-next: build failure after merge of the devicetree 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: <20231208141156.20341c10@canb.auug.org.au>
Date:   Fri, 8 Dec 2023 14:11:56 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Rob Herring <robh@...nel.org>
Cc:     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 devicetree tree

Hi Rob,

On Thu, 7 Dec 2023 16:05:27 -0600 Rob Herring <robh@...nel.org> wrote:
>
> On Thu, Dec 7, 2023 at 2:58 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Thu, 7 Dec 2023 09:11:22 -0600 Rob Herring <robh@...nel.org> wrote:  
> > >
> > > I'm sending out fixes for all these. I want to get the final patch
> > > ("of: Stop circularly including of_device.h and of_platform.h") for
> > > all this in next to get some better build coverage and catch any new
> > > drivers added. But if it is dropped for every new driver that breaks,
> > > I'll never get it in. Can you fix these up or just leave them broken?
> > > I can keep the fixes in my tree until they get applied by the
> > > corresponding subsystem.  
> >
> > These dependencies between trees are impossible to handle.  Please if
> > you really need the final patch in, then you must put all the necessary
> > fixes in the same branch.  There is no telling what order Linus (or I)
> > will merge the interdependent branches.
> >
> > The alternative is to spray the needed fixes out to the other
> > subsystems and then put the final patch in after the merge window
> > closes or the next release.  
> 
> Yes, that's what I've been doing since July and plan to do for the
> final patch. The final patch can't wait a cycle because then we'll
> just have more moles to wack. There's a couple of dependencies that
> still haven't been picked up (seems Sparc is unmaintained), so I'm
> going to send those along. I'll carry any further fixes until they I
> see they are applied.

OK, so I have moved your tree to be merged last and I fixed up the new
driver, so hopefully we are good, now.
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped