linux-kernel - Re: linux-next: build failure after merge of the mm 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: <20240723225732.1e050339cb366c998cfda374@linux-foundation.org>
Date: Tue, 23 Jul 2024 22:57:32 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, 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 mm tree

On Wed, 24 Jul 2024 06:31:53 +0100 Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:

> > Caused by commit
> >
> >   b102945dd5b2 ("mm: move internal core VMA manipulation functions to own file")
> >
> > from the mm-unstable branch of the mm tree.
> >
> > asm/page_types.h only exists for x86 ...
> >
> > I have dropped the mm tree until the end of the merge window.
> >
> 
> This seems a bit drastic. It's literally caused by 2 unncessary header includes
> which are already fixed.
> 
> We really want to get some time in -next for this ideally.

I'm busily merging 6.12 material while the 6.11 merge window is still
open.  That is Against The Rules, for good reasons - linux-next remains
the 6.11-rc1 candidate tree until the merge window ends.

So removing mm.git from -next is appropriate.  It'll be restored next week.

mm-unstable remains a suitable base for ongoing work.