[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250822041538.467514-1-CFSworks@gmail.com>
Date: Thu, 21 Aug 2025 21:15:35 -0700
From: Sam Edwards <cfsworks@...il.com>
To: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Marc Zyngier <maz@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Ard Biesheuvel <ardb@...nel.org>,
Ryan Roberts <ryan.roberts@....com>,
Baruch Siach <baruch@...s.co.il>,
Kevin Brodsky <kevin.brodsky@....com>,
Joey Gouly <joey.gouly@....com>,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Sam Edwards <CFSworks@...il.com>
Subject: [PATCH 0/3] Type correctness cleanup for ARM64 MMU initialization
Hello list,
This is a small series of type correctness and readability improvements for
ARM64's MMU initialization code. When I first encountered this code, the heavy
use of u64 to represent both virtual and physical addresses made it difficult
to understand where the demarcations were. I made most of the changes in this
series while troubleshooting a different problem (fixed in a separate patch) to
make that boundary a little clearer. I am submitting it now in the hopes that
this will improve maintainability and readability for others.
While nothing in this series represents a change in behavior, it is not merely
cosmetic: I believe these changes better align with the kernel's code
standards, type discipline, and common C idioms.
Happy Thursday,
Sam
Sam Edwards (3):
arm64: mm: Cast start/end markers to char *, not u64
arm64: mm: Make map_fdt() return mapped pointer
arm64: mm: Represent physical memory with phys_addr_t and
resource_size_t
arch/arm64/kernel/pi/map_kernel.c | 41 ++++++++++++++++---------------
arch/arm64/kernel/pi/map_range.c | 20 +++++++++------
arch/arm64/kernel/pi/pi.h | 9 ++++---
arch/arm64/mm/init.c | 6 ++---
arch/arm64/mm/mmu.c | 17 +++++++------
5 files changed, 50 insertions(+), 43 deletions(-)
--
2.49.1
Powered by blists - more mailing lists