diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2023-02-10 09:03:39 +0100 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2023-02-12 12:12:36 +0100 |
| commit | 53cea34b0a0a03568e189f8dfe2eb06f938986c8 (patch) | |
| tree | addbbd22bcc69009268dd4bc4cdf2f7406b06b34 /security | |
| parent | powerpc/secvar: Fix incorrect return in secvar_sysfs_load() (diff) | |
| download | linux-53cea34b0a0a03568e189f8dfe2eb06f938986c8.tar.xz linux-53cea34b0a0a03568e189f8dfe2eb06f938986c8.zip | |
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
Diffstat (limited to 'security')
| -rw-r--r-- | security/integrity/platform_certs/load_powerpc.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/security/integrity/platform_certs/load_powerpc.c b/security/integrity/platform_certs/load_powerpc.c index a2900cb85357..1e4f80a4e71c 100644 --- a/security/integrity/platform_certs/load_powerpc.c +++ b/security/integrity/platform_certs/load_powerpc.c @@ -18,7 +18,7 @@ /* * Get a certificate list blob from the named secure variable. */ -static __init void *get_cert_list(u8 *key, unsigned long keylen, uint64_t *size) +static __init void *get_cert_list(u8 *key, unsigned long keylen, u64 *size) { int rc; void *db; @@ -51,7 +51,7 @@ static __init void *get_cert_list(u8 *key, unsigned long keylen, uint64_t *size) static int __init load_powerpc_certs(void) { void *db = NULL, *dbx = NULL; - uint64_t dbsize = 0, dbxsize = 0; + u64 dbsize = 0, dbxsize = 0; int rc = 0; struct device_node *node; |