From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the vfs-brauner tree
Date: Wed, 11 Dec 2024 14:37:01 +1100 [thread overview]
Message-ID: <20241211143701.5cfc95a7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2905 bytes --]
Hi all,
After merging the vfs-brauner tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
samples/vfs/mountinfo.c: In function 'show_propagation':
samples/vfs/mountinfo.c:104:36: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
104 | printf(" shared:%llu", sm->mnt_peer_group);
| ~~~^ ~~~~~~~~~~~~~~~~~~
| | |
| | __u64 {aka long unsigned int}
| long long unsigned int
| %lu
samples/vfs/mountinfo.c:106:36: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
106 | printf(" master:%llu", sm->mnt_master);
| ~~~^ ~~~~~~~~~~~~~~
| | |
| | __u64 {aka long unsigned int}
| long long unsigned int
| %lu
samples/vfs/mountinfo.c:108:52: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
108 | printf(" propagate_from:%llu", sm->propagate_from);
| ~~~^ ~~~~~~~~~~~~~~~~~~
| | |
| | __u64 {aka long unsigned int}
| long long unsigned int
| %lu
samples/vfs/mountinfo.c: In function 'dump_mountinfo':
samples/vfs/mountinfo.c:144:42: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
144 | printf("0x%lx 0x%lx 0x%llx ", mnt_ns_id, mnt_id, buf->mnt_parent_id);
| ~~~^ ~~~~~~~~~~~~~~~~~~
| | |
| long long unsigned int __u64 {aka long unsigned int}
| %lx
Introduced by commits
0c8f746452aa ("samples: add a mountinfo program to demonstrate statmount()/listmount()")
ee8c840a4a35 ("samples: fix missing nodiratime option and handle propagate_from correctly")
I am not sure why these warnings only turned up today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-12-11 3:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 3:37 Stephen Rothwell [this message]
2024-12-19 6:31 ` linux-next: build warnings after merge of the vfs-brauner tree Stephen Rothwell
2024-12-19 12:40 ` Jeff Layton
2024-12-19 20:36 ` Stephen Rothwell
2025-01-06 13:50 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 0:52 Stephen Rothwell
2025-11-17 6:47 Stephen Rothwell
2025-11-12 2:42 Stephen Rothwell
2025-11-12 10:10 ` Mateusz Guzik
2025-11-12 10:55 ` Stephen Rothwell
2025-11-12 10:57 ` Mateusz Guzik
2025-07-17 7:36 Stephen Rothwell
2025-07-22 10:24 ` Jann Horn
2025-03-05 10:07 Stephen Rothwell
2025-03-05 10:55 ` David Disseldorp
2024-12-13 4:27 Stephen Rothwell
2024-12-19 6:32 ` Stephen Rothwell
2025-01-14 5:48 ` Stephen Rothwell
2025-01-20 8:25 ` Stephen Rothwell
2025-01-20 12:15 ` Christian Brauner
2025-01-20 20:55 ` Stephen Rothwell
2024-10-09 6:29 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=20241211143701.5cfc95a7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=jlayton@kernel.org \
--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