Re: [PATCH] staging: fbtft: Fix type mismatch found with sparse

2017-07-05 Thread Dan Carpenter
Someone already sent that.  You could be working against linux-next or
staging-next.

regards,
dan carpenter


___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


[PATCH] staging: fbtft: Fix type mismatch found with sparse

2017-07-03 Thread Thomas Gardner
The warning below is resolved by changing the LHS cast to __be64.

fbtft/fbtft-io.c:74:29: warning: incorrect type in assignment (different base 
types)
fbtft/fbtft-io.c:74:29:expected unsigned long long [unsigned] [long] [long 
long] [usertype] 
fbtft/fbtft-io.c:74:29:got restricted __be64 [usertype] 

Signed-off-by: Thomas Gardner 
---
 drivers/staging/fbtft/fbtft-io.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/fbtft/fbtft-io.c b/drivers/staging/fbtft/fbtft-io.c
index d86840548b74..ffb9a3b4d454 100644
--- a/drivers/staging/fbtft/fbtft-io.c
+++ b/drivers/staging/fbtft/fbtft-io.c
@@ -71,7 +71,7 @@ int fbtft_write_spi_emulate_9(struct fbtft_par *par, void 
*buf, size_t len)
src++;
}
tmp |= ((*src & 0x0100) ? 1 : 0);
-   *(u64 *)dst = cpu_to_be64(tmp);
+   *(__be64 *)dst = cpu_to_be64(tmp);
dst += 8;
*dst++ = (u8)(*src++ & 0x00FF);
added++;
-- 
2.13.2

___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel