u32, therefore
there's a type missmatch here.
Rationale for #239:
Is the dual of #164. This time data going to be written so it
needs to be converted from cpu to __be32, but writel() expects u32 and the
output of cpu_to_be32 returns a __be32.
Signed-off-by: Juan Antonio Aldea-Armen
, therefore
there's a type missmatch here.
Rationale for #293:
Is the dualof #164. This time data going to be written so it
needs to be converted from cpu to be32, but writel() expects u32 and the
output of cpu_to_be32 returns a __be32.
Signed-off-by: Juan Antonio Aldea-Armenteros
---
drivers/st
No I didn't intent to. I have sent another version.
Thank you very much, Dan.
Juan Antonio Aldea-Armenteros
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
114.c:236:
+ v4l2_err(client, "misensor_rmw_reg error exit, write failed\n");
Signed-off-by: Juan Antonio Aldea-Armenteros
---
PATCH V2:
* Restored word "error" as pointed out by Dan Carpenter
PATCH V3:
* Fix V2 changelog message.
drivers/staging/media/atomisp/i
114.c:236:
+ v4l2_err(client, "misensor_rmw_reg error exit, write failed\n");
Signed-off-by: Juan Antonio Aldea-Armenteros
PATCH V2:
* Restored word "error" as pointed out by Dan Carpenter
---
drivers/staging/media/atomisp/i2c/atomisp-mt9m114.c | 4 ++--
1 file change
114.c:236:
+ v4l2_err(client, "misensor_rmw_reg error exit, write failed\n");
Signed-off-by: Juan Antonio Aldea-Armenteros
---
drivers/staging/media/atomisp/i2c/atomisp-mt9m114.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/
