> Can't we fix this properly, to use the correct type of pointer instead
> for non-__iomem allocations?
You mean making an alternate screen_base pointer inside fb_info that
isn't __iomem? There are already a bunch of framebuffer drivers that
(ab)use screen_base to store non-__iomem pointers, so t
erent address spaces)
drivers/staging/fbtft/fbtft-core.c:918:19:expected void const *addr
drivers/staging/fbtft/fbtft-core.c:918:19:got char [noderef]
*screen_base
Signed-off-by: Garret Kelly
---
drivers/staging/fbtft/fbtft-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Fix two instances of the following checkpatch warning:
WARNING: Missing a blank line after declarations
Signed-off-by: Garret Kelly
---
drivers/staging/goldfish/goldfish_audio.c | 1 +
drivers/staging/goldfish/goldfish_nand.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers
3 matches
Mail list logo