From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jpirko-mlxsw:wip_attestation_pre_rfc_draft1 17/26] ctlv.c:1740:52: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 5 has type '__u64' {aka 'long unsigned int'}
Date: Wed, 30 Sep 2026 09:50:15 +0200 [thread overview]
Message-ID: <202609300903.dKo7SR8n-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jiri Pirko <jiri@nvidia.com>
tree: https://github.com/jpirko/linux_mlxsw wip_attestation_pre_rfc_draft1
head: a18af4e1b514bf11f88ca42d29b7b68f3b375378
commit: 632e6dd46feb3a874a82d83535f9e3fd973231b3 [17/26] selftests/ctlv: Add the wire-format selftests
:::::: branch date: 13 hours ago
:::::: commit date: 4 days ago
config: powerpc64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260930/202609300903.dKo7SR8n-lkp@intel.com/config)
compiler: powerpc64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260930/202609300903.dKo7SR8n-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202609300903.dKo7SR8n-lkp@intel.com/
All warnings (new ones prefixed by >>):
ctlv.c: In function 'device_a_continuation_of_a_series_that_moved_on':
>> ctlv.c:1740:52: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 5 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
1740 | "reason=%u expected-generation=%llu current-generation=%llu",
| ~~~^
| |
| long long unsigned int
| %lu
1741 | CTLV_VALIDATION_REASON_STALE_GENERATION, generation,
| ~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
ctlv.c:1740:76: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 6 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
1740 | "reason=%u expected-generation=%llu current-generation=%llu",
| ~~~^
| |
| long long unsigned int
| %lu
1741 | CTLV_VALIDATION_REASON_STALE_GENERATION, generation,
1742 | generation + 1);
| ~~~~~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
ctlv.c: In function 'intro_an_availability_change_between_two_fragments':
ctlv.c:2416:52: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 5 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
2416 | "reason=%u expected-generation=%llu current-generation=%llu",
| ~~~^
| |
| long long unsigned int
| %lu
2417 | CTLV_VALIDATION_REASON_STALE_GENERATION, generation,
| ~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
ctlv.c:2416:76: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 6 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
2416 | "reason=%u expected-generation=%llu current-generation=%llu",
| ~~~^
| |
| long long unsigned int
| %lu
2417 | CTLV_VALIDATION_REASON_STALE_GENERATION, generation,
2418 | generation + 1);
| ~~~~~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-30 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609300903.dKo7SR8n-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.