Yes, it is not I/O memory address. I was wrong on that.
But it makes sparse happy.
Is here any side effect of using ioread16() ?
regards,
ronit
On Tue, Aug 18, 2015 at 2:27 PM, Dan Carpenter wrote:
> On Tue, Aug 18, 2015 at 12:16:57PM +0530, Ronit Halder wrote:
>> This patch fixes the warning ge
On Tue, Aug 18, 2015 at 12:16:57PM +0530, Ronit Halder wrote:
> This patch fixes the warning generated by sparse
> "cast removes address space of expression" by using ioread16
> function insted of directly dereferencing I/O memory.
>
> Signed-off-by: Ronit halder
Are these really iomem pointers?
This patch fixes the warning generated by sparse
"cast removes address space of expression" by using ioread16
function insted of directly dereferencing I/O memory.
Signed-off-by: Ronit halder
---
drivers/staging/fbtft/fb_agm1264k-fl.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
d
