powerpc/secvar: Use u64 in secvar_operations
authorMichael Ellerman <mpe@ellerman.id.au>
Fri, 10 Feb 2023 08:03:39 +0000 (19:03 +1100)
committerMichael Ellerman <mpe@ellerman.id.au>
Sun, 12 Feb 2023 11:12:36 +0000 (22:12 +1100)
commit53cea34b0a0a03568e189f8dfe2eb06f938986c8
treeaddbbd22bcc69009268dd4bc4cdf2f7406b06b34
parentc9fd2952754a03b2c14433c0318f4b46e9c0f2ef
powerpc/secvar: Use u64 in secvar_operations

There's no reason for secvar_operations to use uint64_t vs the more
common kernel type u64.

The types are compatible, but they require different printk format
strings which can lead to confusion.

Change all the secvar related routines to use u64.

Reviewed-by: Russell Currey <ruscur@russell.cc>
Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com>
Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20230210080401.345462-5-ajd@linux.ibm.com
arch/powerpc/include/asm/secvar.h
arch/powerpc/kernel/secvar-sysfs.c
arch/powerpc/platforms/powernv/opal-secvar.c
security/integrity/platform_certs/load_powerpc.c