From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Srikanth Jampala <Jampala.Srikanth@cavium.com>
Subject: linux-next: build warning after merge of the crypto tree
Date: Fri, 5 Oct 2018 15:31:07 +1000 [thread overview]
Message-ID: <20181005153107.26147ecc@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
drivers/crypto/cavium/nitrox/nitrox_debugfs.c: In function 'stats_show':
drivers/crypto/cavium/nitrox/nitrox_debugfs.c:62:30: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type 'long int' [-Wformat=]
seq_printf(s, " Posted: %lld\n", atomic64_read(&ndev->stats.posted));
~~~^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
%ld
drivers/crypto/cavium/nitrox/nitrox_debugfs.c:63:33: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type 'long int' [-Wformat=]
seq_printf(s, " Completed: %lld\n",
~~~^
%ld
atomic64_read(&ndev->stats.completed));
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/crypto/cavium/nitrox/nitrox_debugfs.c:65:31: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type 'long int' [-Wformat=]
seq_printf(s, " Dropped: %lld\n", atomic64_read(&ndev->stats.dropped));
~~~^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
%ld
Introduced by commit
2a8780be9c26 ("crypto: cavium/nitrox - updated debugfs information.")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-10-05 5:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 5:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 3:48 linux-next: build warning after merge of the crypto tree Stephen Rothwell
2024-02-12 12:59 ` Cabiddu, Giovanni
2022-11-21 1:52 Stephen Rothwell
2022-07-11 10:49 Stephen Rothwell
2019-08-23 3:14 Stephen Rothwell
2019-08-25 18:01 ` Hans de Goede
2019-02-04 0:01 Stephen Rothwell
2018-03-19 1:04 Stephen Rothwell
2018-03-19 5:44 ` Harsh Jain
2018-01-19 1:49 Stephen Rothwell
2018-01-19 4:21 ` Harsh Jain
2018-01-19 5:12 ` Herbert Xu
2017-07-31 2:17 Stephen Rothwell
2017-07-31 13:50 ` Gary R Hook
2016-08-25 1:38 Stephen Rothwell
2016-08-25 6:20 ` Martin Schwidefsky
2016-08-25 7:47 ` Herbert Xu
2016-08-25 11:14 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181005153107.26147ecc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jampala.Srikanth@cavium.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).