linux-kernel - linux-next: manual merge of the arm64 tree with Linus' 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>] [day] [month] [year] [list]

Message-ID: <20251113095540.4a66405f@canb.auug.org.au>
Date: Thu, 13 Nov 2025 09:55:40 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Marc Zyngier <maz@...nel.org>,
 mrigendrachaubey <mrigendra.chaubey@...il.com>
Subject: linux-next: manual merge of the arm64 tree with Linus' tree

Hi all,

Today's linux-next merge of the arm64 tree got a conflict in:

  arch/arm64/include/asm/el2_setup.h

between commit:

  ca88ecdce5f5 ("arm64: Revamp HCR_EL2.E2H RES1 detection")

from Linus' tree and commit:

  96ac403ea2b4 ("arm64: Fix typos and spelling errors in comments")

from the arm64 tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/arm64/include/asm/el2_setup.h
index 99a7c0235e6d,cb0d72401d45..000000000000
--- a/arch/arm64/include/asm/el2_setup.h
+++ b/arch/arm64/include/asm/el2_setup.h
@@@ -24,7 -24,11 +24,7 @@@
  	 * ID_AA64MMFR4_EL1.E2H0 < 0. On such CPUs HCR_EL2.E2H is RES1, but it
  	 * can reset into an UNKNOWN state and might not read as 1 until it has
  	 * been initialized explicitly.
- 	 * Initalize HCR_EL2.E2H so that later code can rely upon HCR_EL2.E2H
 -	 *
 -	 * Fruity CPUs seem to have HCR_EL2.E2H set to RAO/WI, but
 -	 * don't advertise it (they predate this relaxation).
 -	 *
+ 	 * Initialize HCR_EL2.E2H so that later code can rely upon HCR_EL2.E2H
  	 * indicating whether the CPU is running in E2H mode.
  	 */
  	mrs_s	x1, SYS_ID_AA64MMFR4_EL1

Content of type "application/pgp-signature" skipped