Currently this is defined the same way for all architectures, and uses types that should size themselves appropriately on most architectures (phys_addr_t uses uintptr_t, virt_addr_t uses void*), but there may be other types we want to define that could benefit from being architecture-dependent. This in theory could be added much later down the line the first time we encounter such a situation, but it's worth considering now.
Currently this is defined the same way for all architectures, and uses types that should size themselves appropriately on most architectures (
phys_addr_tusesuintptr_t,virt_addr_tusesvoid*), but there may be other types we want to define that could benefit from being architecture-dependent. This in theory could be added much later down the line the first time we encounter such a situation, but it's worth considering now.