From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Mickaël Salaün" <mic@digikod•net>
Cc: Konstantin Meskhidze <konstantin.meskhidze@huawei•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the landlock tree
Date: Wed, 7 Jun 2023 13:52:29 +1000 [thread overview]
Message-ID: <20230607135229.1f1e5c91@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hi all,
After merging the landlock tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
samples/landlock/sandboxer.c: In function 'populate_ruleset_net':
samples/landlock/sandboxer.c:190:78: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
190 | "Failed to update the ruleset with port \"%lld\": %s\n",
| ~~~^
| |
| long long int
| %ld
191 | net_service.port, strerror(errno));
| ~~~~~~~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
Introduced by commit
1c5befb13501 ("samples/landlock: Add network demo")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-07 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 3:52 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 3:27 linux-next: build warning after merge of the landlock tree Stephen Rothwell
[not found] ` <20230920092641.832134-12-konstantin.meskhidze@huawei.com>
2023-10-03 13:15 ` Mickaël Salaün
2023-10-03 13:23 ` Geert Uytterhoeven
2023-10-04 11:01 ` Mickaël Salaün
2023-10-03 13:40 ` Arnd Bergmann
2023-10-04 11:02 ` Mickaël Salaün
2023-11-17 1:04 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=20230607135229.1f1e5c91@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=konstantin.meskhidze@huawei$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mic@digikod$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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