Michael Ellerman 53cea34b0a 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		2023-02-12 22:12:36 +11:00
..
evm	lsm/stable-6.2 PR 20221212	2022-12-13 09:47:48 -08:00
ima	fs.vfsuid.ima.v6.2-rc1	2022-12-21 08:13:01 -08:00
platform_certs	powerpc/secvar: Use u64 in secvar_operations	2023-02-12 22:12:36 +11:00
digsig_asymmetric.c	ima: fix reference leak in asymmetric_verify()	2022-01-24 18:37:36 -05:00
digsig.c	integrity: Fix memory leakage in keyring allocation error path	2022-11-16 11:47:47 -05:00
iint.c	evm: Load EVM key in ima_load_x509() to avoid appraisal	2021-05-21 12:47:04 -04:00
integrity_audit.c	integrity: check the return value of audit_log_start()	2022-02-02 11:44:23 -05:00
integrity.h	ima: support fs-verity file digest based version 3 signatures	2022-05-05 17:41:51 -04:00
Kconfig	integrity: Introduce a Linux keyring called machine	2022-03-08 13:55:52 +02:00
Makefile	integrity: Introduce a Linux keyring called machine	2022-03-08 13:55:52 +02:00