[PATCH 0/3] Type correctness cleanup for ARM64 MMU initialization

Sam Edwards posted 3 patches 1 month, 1 week ago
There is a newer version of this series
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(-)
[PATCH 0/3] Type correctness cleanup for ARM64 MMU initialization
Posted by Sam Edwards 1 month, 1 week ago
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