diff options
| author | Arnd Bergmann | 2017-03-20 13:39:16 +0100 |
|---|---|---|
| committer | Herbert Xu | 2017-03-24 15:03:01 +0100 |
| commit | d64069ee1869b9f77eef0bf9dfceffee2bfd7692 (patch) | |
| tree | d2916b23c6cab977c7898be57dc762d9dd69229c /crypto/testmgr.c | |
| parent | crypto: zip - Memory corruption in zip_clear_stats() (diff) | |
| download | kernel-qcow2-linux-d64069ee1869b9f77eef0bf9dfceffee2bfd7692.tar.gz kernel-qcow2-linux-d64069ee1869b9f77eef0bf9dfceffee2bfd7692.tar.xz kernel-qcow2-linux-d64069ee1869b9f77eef0bf9dfceffee2bfd7692.zip | |
crypto: zip - add a cast for printing atomic64_t values
kernelci.org reports a build-time regression on linux-next, with a harmless
warning in x86 allmodconfig:
drivers/crypto/cavium/zip/zip_main.c:489:18: warning: format '%ld' expects argument of type 'long int', but argument 7 has type 'long long int' [-Wformat=]
drivers/crypto/cavium/zip/zip_main.c:489:18: warning: format '%ld' expects argument of type 'long int', but argument 6 has type 'long long int' [-Wformat=]
drivers/crypto/cavium/zip/zip_main.c:489:18: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'long long int' [-Wformat=]
The return type for atomic64_read() unfortunately differs between
architectures, with some defining it as atomic_long_read() and others
returning a 64-bit type explicitly. Fixing this in general would be nice,
but also require changing other users of these functions, so the simpler
workaround is to add a cast here that avoids the warnings on the default
build.
Fixes: 09ae5d37e093 ("crypto: zip - Add Compression/Decompression statistics")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions