linux-kernel - Re: linux-next: manual merge of the arm64 tree with the origin 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: <abb2c706-d599-43b5-8277-37d85efe96b5@sirena.org.uk>
Date: Mon, 26 Jan 2026 16:08:09 +0000
From: Mark Brown <broonie@...nel.org>
To: Will Deacon <will@...nel.org>
Cc: maz@...nel.org, Catalin Marinas <catalin.marinas@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Oliver Upton <oupton@...nel.org>,
	Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: linux-next: manual merge of the arm64 tree with the origin tree

On Mon, Jan 26, 2026 at 03:23:32PM +0000, Will Deacon wrote:
> On Mon, Jan 26, 2026 at 03:11:27PM +0000, Mark Brown wrote:

> > [Took the version from Linus' tree.]

> Hmm, I suspect that's not quite right because CONFIG_ARM64_PAN doesn't
> exist anymore in the arm64 tree and so the hunk in
> arch/arm64/kvm/va_layout.c probably needs tweaking.

Indeed - there's updates needed elsewhere.

> Marc -- how would you prefer to handle this? I could bring back
> CONFIG_ARM64_PAN as a hidden Kconfig option =y and then we could clean
> up the stragglers at -rc1?

I guess you could also merge up -rc7 given that this is in Linus' tree?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)