Hi! Building vop with make C=1 produces the following: CHECK drivers/misc/mic/vop/vop_main.c drivers/misc/mic/vop/vop_main.c:551:58: warning: incorrect type in argument 1 (different address spaces) drivers/misc/mic/vop/vop_main.c:551:58: expected void const volatile [noderef] __iomem *addr drivers/misc/mic/vop/vop_main.c:551:58: got restricted __le64 * drivers/misc/mic/vop/vop_main.c:560:49: warning: incorrect type in argument 1 (different address spaces) drivers/misc/mic/vop/vop_main.c:560:49: expected struct mic_device_ctrl *dc drivers/misc/mic/vop/vop_main.c:560:49: got struct mic_device_ctrl [noderef] __iomem *dc drivers/misc/mic/vop/vop_main.c:579:49: warning: incorrect type in argument 1 (different address spaces) drivers/misc/mic/vop/vop_main.c:579:49: expected struct mic_device_ctrl *dc drivers/misc/mic/vop/vop_main.c:579:49: got struct mic_device_ctrl [noderef] __iomem *dc
Would be nice to fix to silence the noise, but I'm not 100% sure what the right thing to do here is. Tag struct members with __iomem or cast with __force on use? -- MST