linux-kernel - Re: linux-next: build failure after merge of the sysctl 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: <C1E2DB59-6064-4871-8F01-369AE6121E48@canb.auug.org.au>
Date: Sat, 01 Nov 2025 22:16:50 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Joel Granados <joel.granados@...nel.org>
CC: Luis Chamberlain <mcgrof@...nel.org>, Kees Cook <kees@...nel.org>,
 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 sysctl tree

On 1 November 2025 12:42:46 am AEDT, Joel Granados <joel.granados@...nel.org> wrote:
>On Fri, Oct 31, 2025 at 09:49:58AM +1100, Stephen Rothwell wrote:
>> Hi all,
>> 
>> After merging the sysctl tree, today's linux-next build (powerpc
>> ppc64_defconfig) failed like this:
>Is it *only* powerpc. Right? I'll take a look at this ASAP.


Hi Joel,

powerpc was just the first build I did, so out is possible that there are other
architectures and/or configs that also do not implicitly include the needed
files.

Cheers,
Stephen Rothwell
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.