Re: [PATCH] vop: Add missing __iomem annotation in vop_dc_to_vdev()

2020-08-03 Thread Michael S. Tsirkin
On Sun, Aug 02, 2020 at 04:28:12PM -0700, Ashutosh Dixit wrote: > Fix the following sparse warnings in drivers/misc/mic/vop//vop_main.c: > > 551:58: warning: incorrect type in argument 1 (different address spaces) > 551:58:expected void const volatile [noderef] __iomem *addr > 551:58:got

Re: [PATCH] vop: Add missing __iomem annotation in vop_dc_to_vdev()

2020-08-02 Thread Dixit, Ashutosh
On Sun, 02 Aug 2020 21:24:01 -0700, Greg Kroah-Hartman wrote: > > On Sun, Aug 02, 2020 at 04:28:12PM -0700, Ashutosh Dixit wrote: > > Fix the following sparse warnings in drivers/misc/mic/vop//vop_main.c: > > > > 551:58: warning: incorrect type in argument 1 (different address spaces) > > 551:58:

Re: [PATCH] vop: Add missing __iomem annotation in vop_dc_to_vdev()

2020-08-02 Thread Greg Kroah-Hartman
On Sun, Aug 02, 2020 at 04:28:12PM -0700, Ashutosh Dixit wrote: > Fix the following sparse warnings in drivers/misc/mic/vop//vop_main.c: > > 551:58: warning: incorrect type in argument 1 (different address spaces) > 551:58:expected void const volatile [noderef] __iomem *addr > 551:58:got

[PATCH] vop: Add missing __iomem annotation in vop_dc_to_vdev()

2020-08-02 Thread Ashutosh Dixit
Fix the following sparse warnings in drivers/misc/mic/vop//vop_main.c: 551:58: warning: incorrect type in argument 1 (different address spaces) 551:58:expected void const volatile [noderef] __iomem *addr 551:58:got restricted __le64 * 560:49: warning: incorrect type in argument 1