linux-kernel - Re: linux-next: build failure after merge of the backlight 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: <20240308063000.6fdce0e5@canb.auug.org.au>
Date: Fri, 8 Mar 2024 06:30:00 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Lee Jones <lee@...nel.org>
Cc: Duje Mihanović <duje.mihanovic@...le.hr>, 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 backlight tree

Hi Lee,

On Thu, 7 Mar 2024 09:04:46 +0000 Lee Jones <lee@...nel.org> wrote:
>
> On Thu, 07 Mar 2024, Lee Jones wrote:
> 
> > Right.  So you build each tree as its merged?

More or less.  I do some batches of merges (since otherwise it just
takes way to long).

> > My assumption was that all things come together in -next? 

This is from my daily summary report:

"Between each merge, the tree was built with a ppc64_defconfig
for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm
and a native build of tools/perf."

> Okay, all patches are now shared between both branches.

Thanks.

> Let me know if there is still an issue.

Will do.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped