From: kernel test robot <lkp@intel.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [cris:scmi_telemetry_ng_V15 10/35] include/linux/printk.h:109:25: warning: format '%llX' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'}
Date: Mon, 09 Nov 2026 14:12:38 +0100 [thread overview]
Message-ID: <202611091427.c6pFGLd7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cris/linux.git scmi_telemetry_ng_V15
head: d51f22cab86f4ad2f08b4e88803f85fdffd81a62
commit: 64c4292f50171fb197737a97cf5cd8b6d378984f [10/35] firmware: arm_scmi: Add Telemetry resources enumeration
config: csky-randconfig-2200-20261109 (https://download.01.org/0day-ci/archive/20261109/202611091427.c6pFGLd7-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 16.2.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261109/202611091427.c6pFGLd7-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/oe-kbuild-all/202611091427.c6pFGLd7-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/device.h:15,
from drivers/firmware/arm_scmi/telemetry.c:13:
drivers/firmware/arm_scmi/telemetry.c: In function 'scmi_telemetry_area_check':
>> include/linux/printk.h:109:25: warning: format '%llX' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'} [-Wformat=]
109 | #define FW_BUG "[Firmware Bug]: "
| ^~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:110:30: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:154:56: note: in expansion of macro 'dev_fmt'
154 | dev_printk_index_wrap(_dev_err, KERN_ERR, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:355:17: note: in expansion of macro 'dev_err'
355 | dev_err(dev, FW_BUG "%s phys_addr (0x%llX) pointer too big.\n",
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:355:30: note: in expansion of macro 'FW_BUG'
355 | dev_err(dev, FW_BUG "%s phys_addr (0x%llX) pointer too big.\n",
| ^~~~~~
>> include/linux/printk.h:109:25: warning: format '%llX' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'} [-Wformat=]
109 | #define FW_BUG "[Firmware Bug]: "
| ^~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:110:30: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:154:56: note: in expansion of macro 'dev_fmt'
154 | dev_printk_index_wrap(_dev_err, KERN_ERR, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:361:17: note: in expansion of macro 'dev_err'
361 | dev_err(dev, FW_BUG "%s phys_addr (0x%llX) misaligned.\n",
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:361:30: note: in expansion of macro 'FW_BUG'
361 | dev_err(dev, FW_BUG "%s phys_addr (0x%llX) misaligned.\n",
| ^~~~~~
>> include/linux/printk.h:109:25: warning: format '%llX' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'} [-Wformat=]
109 | #define FW_BUG "[Firmware Bug]: "
| ^~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:110:30: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:154:56: note: in expansion of macro 'dev_fmt'
154 | dev_printk_index_wrap(_dev_err, KERN_ERR, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:373:17: note: in expansion of macro 'dev_err'
373 | dev_err(dev, FW_BUG "%s area (0x%llX/%u) wrap-around.\n",
| ^~~~~~~
drivers/firmware/arm_scmi/telemetry.c:373:30: note: in expansion of macro 'FW_BUG'
373 | dev_err(dev, FW_BUG "%s area (0x%llX/%u) wrap-around.\n",
| ^~~~~~
vim +109 include/linux/printk.h
968ab1838a5d48f Linus Torvalds 2010-11-15 88
968ab1838a5d48f Linus Torvalds 2010-11-15 89 /*
968ab1838a5d48f Linus Torvalds 2010-11-15 90 * FW_BUG
968ab1838a5d48f Linus Torvalds 2010-11-15 91 * Add this to a message where you are sure the firmware is buggy or behaves
968ab1838a5d48f Linus Torvalds 2010-11-15 92 * really stupid or out of spec. Be aware that the responsible BIOS developer
968ab1838a5d48f Linus Torvalds 2010-11-15 93 * should be able to fix this issue or at least get a concrete idea of the
968ab1838a5d48f Linus Torvalds 2010-11-15 94 * problem by reading your message without the need of looking at the kernel
968ab1838a5d48f Linus Torvalds 2010-11-15 95 * code.
968ab1838a5d48f Linus Torvalds 2010-11-15 96 *
968ab1838a5d48f Linus Torvalds 2010-11-15 97 * Use it for definite and high priority BIOS bugs.
968ab1838a5d48f Linus Torvalds 2010-11-15 98 *
968ab1838a5d48f Linus Torvalds 2010-11-15 99 * FW_WARN
968ab1838a5d48f Linus Torvalds 2010-11-15 100 * Use it for not that clear (e.g. could the kernel messed up things already?)
968ab1838a5d48f Linus Torvalds 2010-11-15 101 * and medium priority BIOS bugs.
968ab1838a5d48f Linus Torvalds 2010-11-15 102 *
968ab1838a5d48f Linus Torvalds 2010-11-15 103 * FW_INFO
968ab1838a5d48f Linus Torvalds 2010-11-15 104 * Use this one if you want to tell the user or vendor about something
968ab1838a5d48f Linus Torvalds 2010-11-15 105 * suspicious, but generally harmless related to the firmware.
968ab1838a5d48f Linus Torvalds 2010-11-15 106 *
968ab1838a5d48f Linus Torvalds 2010-11-15 107 * Use it for information or very low priority BIOS bugs.
968ab1838a5d48f Linus Torvalds 2010-11-15 108 */
968ab1838a5d48f Linus Torvalds 2010-11-15 @109 #define FW_BUG "[Firmware Bug]: "
968ab1838a5d48f Linus Torvalds 2010-11-15 110 #define FW_WARN "[Firmware Warn]: "
968ab1838a5d48f Linus Torvalds 2010-11-15 111 #define FW_INFO "[Firmware Info]: "
968ab1838a5d48f Linus Torvalds 2010-11-15 112
:::::: The code at line 109 was first introduced by commit
:::::: 968ab1838a5d48f02f5b471aa1d0e59e2cc2ccbc include/linux/kernel.h: Move logging bits to include/linux/printk.h
:::::: TO: Linus Torvalds <torvalds@linux-foundation.org>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-11-09 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-09 13:20 [cris:scmi_telemetry_ng_V15 10/35] include/linux/printk.h:109:25: warning: format '%llX' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'} kernel test robot
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=202611091427.c6pFGLd7-lkp@intel.com \
--to=lkp@intel.com \
--cc=cristian.marussi@arm.com \
--cc=oe-kbuild-all@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.