:::::: 
:::::: Manual check reason: "low confidence static check first_new_problem: 
drivers/hwmon/asb100.c:243:1: warning: %d in format string (no. 1) requires 
'int' but the argument type is 'unsigned int'. [invalidPrintfArgType_sint]"
:::::: 

BCC: [email protected]
CC: [email protected]
CC: [email protected]
TO: "Uwe Kleine-König" <[email protected]>
CC: Guenter Roeck <[email protected]>
CC: Jean Delvare <[email protected]>

Hi Uwe,

FYI, the error/warning was bisected to this commit, please ignore it if it's 
irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
master
head:   7e18e42e4b280c85b76967a9106a13ca61c16179
commit: b97adb596399581df42a5f94e14235359f150373 hwmon: Allow to compile ASB100 
and FSCHMD on !X86
date:   8 weeks ago
:::::: branch date: 24 hours ago
:::::: commit date: 8 weeks ago
compiler: alpha-linux-gcc (GCC) 12.1.0
reproduce (cppcheck warning):
        # apt-get install cppcheck
        git checkout b97adb596399581df42a5f94e14235359f150373
        cppcheck --quiet --enable=style,performance,portability --template=gcc 
FILE

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>


vim +243 drivers/hwmon/asb100.c

^1da177e4c3f41 drivers/i2c/chips/asb100.c Linus Torvalds 2005-04-16  242  
^1da177e4c3f41 drivers/i2c/chips/asb100.c Linus Torvalds 2005-04-16 @243  
show_in_reg(in)
^1da177e4c3f41 drivers/i2c/chips/asb100.c Linus Torvalds 2005-04-16  244  
show_in_reg(in_min)
^1da177e4c3f41 drivers/i2c/chips/asb100.c Linus Torvalds 2005-04-16  245  
show_in_reg(in_max)
^1da177e4c3f41 drivers/i2c/chips/asb100.c Linus Torvalds 2005-04-16  246  

:::::: The code at line 243 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2

:::::: TO: Linus Torvalds <[email protected]>
:::::: CC: Linus Torvalds <[email protected]>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
kbuild mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to