On 5/18/22 17:55, kernel test robot wrote:
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 736ee37e2e8eed7fe48d0a37ee5a709514d478b3 Add linux-next specific
files for 20220518
Error/Warning reports:
https://lore.kernel.org/linux-mm/202204291924.vtgzmeri-...@intel.com
https://lore.kernel.org/linux-mm/202205041248.wgcwpcev-...@intel.com
https://lore.kernel.org/linux-mm/202205122113.ulkzd3sz-...@intel.com
https://lore.kernel.org/linux-mm/202205172344.3gfeaum1-...@intel.com
https://lore.kernel.org/linux-mm/202205190527.o9wvevhi-...@intel.com
Error/Warning: (recently discovered and may have been fixed)
[ .. ]
drivers/hwmon/nct6775-platform.c:199:9: sparse: unsigned char
drivers/hwmon/nct6775-platform.c:199:9: sparse: void
This is getting tiresome. Every driver using outb() on m68k will
experience that "problem". As far as I can see, it is caused by
#define out_8(addr,b) (void)((*(__force volatile u8 *) (unsigned long)(addr)) =
(b))
in arch/m68k/include/asm/raw_io.h. I have no idea what the
"(void)" is for, but removing it "fixes" the problem.
Either case, this is not a problem with the nct6775 driver,
nor is it a new problem.
Guenter
