From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the fsinfo tree
Date: Thu, 14 May 2020 19:10:36 +1000 [thread overview]
Message-ID: <20200514191036.0e7bdcc8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
Hi all,
After merging the fsinfo tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
samples/vfs/test-fsinfo.c: In function 'dump_fsinfo_generic_statfs':
samples/vfs/test-fsinfo.c:135:30: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
135 | printf("\tbsize : %llu\n", f->f_bsize);
| ~~~^ ~~~~~~~~~~
| | |
| | __u64 {aka long unsigned int}
| long long unsigned int
| %lu
samples/vfs/test-fsinfo.c:136:30: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
136 | printf("\tfrsize : %llu\n", f->f_frsize);
| ~~~^ ~~~~~~~~~~~
| | |
| | __u64 {aka long unsigned int}
| long long unsigned int
| %lu
Introduced by commit
1b3979fc0f0c ("fsinfo: Add fsinfo() syscall to query filesystem information")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-14 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 9:10 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 10:22 linux-next: build warning after merge of the fsinfo tree Stephen Rothwell
2020-05-12 23:27 ` David Howells
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=20200514191036.0e7bdcc8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--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).