In fbtft-bus.c:fbtft_write_vmem16_bus9(), ioread8() is used for
accessing the provided screen array. Since screen_buffer actually
points to an ordinary buffer, instead access it directly.
Signed-off-by: Lars Svensson
---
drivers/staging/fbtft/fbtft-bus.c | 8
1 file changed, 4
Some drivers use member screen_base of struct fb_info to store non-
__iomem pointers, creating the need for ugly __force typecasts to
avoid sparse warnings. This adds an alternate pointer without the
__iomem qualifyer for this use.
Signed-off-by: Lars Svensson
---
Patch v3: bugfix in fbtft
Member screen_base in struct fb_info is declared with __iomem
qualifier causing sparse warnings when used as a regular ponter.
To avoid the warnings, instead use alternate non-__iomem pointer,
screen_buffer, troughout the driver.
Signed-off-by: Lars Svensson
---
drivers/staging/fbtft
Some drivers use member screen_base of struct fb_info to store non-
__iomem pointers, creating the need for ugly __force typecasts to
avoid sparse warnings. This adds an alternate pointer without the
__iomem qualifyer for this use.
Signed-off-by: Lars Svensson
---
include/linux/fb.h | 5
Member screen_base in struct fb_info is declared with __iomem
qualifier causing sparse warnings when used as a regular ponter.
To avoid the warnings, instead use alternate non-__iomem pointer,
screen_buffer, troughout the driver.
Signed-off-by: Lars Svensson
---
v2: removed all references to
:expected void const *addr
fbtft-core.c:922:39:got char [noderef] *screen_base
Signed-off-by: Lars Svensson
---
drivers/staging/fbtft/fbtft-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft-core.c
b/drivers/staging/fbtft/fbtft-core.c
Some drivers use member screen_base of struct fb_info to store non-
__iomem pointers, creating the need for ugly __force typecasts to
avoid sparse warnings. This adds an alternate pointer without the
__iomem qualifyer for this use.
Signed-off-by: Lars Svensson
---
New version of my previous
void const *addr
fbtft-core.c:922:39:got char [noderef] *screen_base
Signed-off-by: Lars Svensson
---
drivers/staging/fbtft/fbtft-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fbtft/fbtft-core.c
b/drivers/staging/fbtft/fbtft-core.c
index 7f5fa3d
/rtl8723au/core/rtw_security.c:776:22: \
warning: cast to restricted __le32
drivers/staging/rtl8723au/core/rtw_security.c:777:24: \
warning: cast to restricted __le32
Signed-off-by: Lars Svensson
---
Patch V2: Reworked as adviced.
---
drivers/staging/rtl8723au/core/rtw_security.c | 9 -
1 file
On Tue, Sep 22, 2015 at 11:30:54PM +0200, Larry Finger wrote:
>
> You may have silenced the Sparse warnings, but the code was not wrong. Your
> version is also correct; however, you end up with some really ugly casts.
>
> Here is my analysis of these two, identical sections:
>
> The output of g
to restricted __le32
drivers/staging/rtl8723au/core/rtw_security.c:776:22: \
warning: cast to restricted __le32
drivers/staging/rtl8723au/core/rtw_security.c:777:24: \
warning: cast to restricted __le32
Signed-off-by: Lars Svensson
---
drivers/staging/rtl8723au/core/rtw_security.c | 15
Fixing indentation errors in
drivers/staging/iio/iio_simple_dummy_events.c.
Signed-off-by: Lars Svensson
---
drivers/staging/iio/iio_simple_dummy_events.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/iio_simple_dummy_events.c
b/drivers/staging/iio
12 matches
Mail list logo