[PATCH 3/4] staging: vt6655: fix wrong parameter as reported by sparse

From: mathieu . poirier
Date: Sat Jan 17 2015 - 21:05:47 EST


From: Mathieu Poirier <mathieu.poirier@xxxxxxxxxx>

mpoirier@t430:~/work/kernel1$ make C=1 M=drivers/staging/vt6655/
LD drivers/staging/vt6655/built-in.o
CHECK drivers/staging/vt6655/device_main.c
CC [M] drivers/staging/vt6655/device_main.o
CHECK drivers/staging/vt6655/card.c
CC [M] drivers/staging/vt6655/card.o
CHECK drivers/staging/vt6655/channel.c
CC [M] drivers/staging/vt6655/channel.o
CHECK drivers/staging/vt6655/mac.c
CC [M] drivers/staging/vt6655/mac.o
CHECK drivers/staging/vt6655/baseband.c
drivers/staging/vt6655/baseband.c:2180:45: warning: incorrect type in argument 1 (different address spaces)
drivers/staging/vt6655/baseband.c:2180:45: expected struct vnt_private *priv
drivers/staging/vt6655/baseband.c:2180:45: got void [noderef] <asn:2>*dwIoBase
CC [M] drivers/staging/vt6655/baseband.o

Since
8e8a9f5133cf staging: vt6655: BBbReadEmbedded replace __iomem with vnt_private

The first parameter to @BBbReadEmbedde is a vnt_private. The patch is changing
all occurences _except_ this one, as reported by sparse.

Signed-off-by: Mathieu Poirier <mathieu.poirier@xxxxxxxxxx>
---
drivers/staging/vt6655/baseband.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
index 86c72ba0a0cd..f8c5fc371c4c 100644
--- a/drivers/staging/vt6655/baseband.c
+++ b/drivers/staging/vt6655/baseband.c
@@ -2177,7 +2177,7 @@ bool BBbVT3253Init(struct vnt_private *priv)
/* Init ANT B select,RX Config CR10 = 0x28->0x2A, 0x2A->0x28(VC1/VC2 define, make the ANT_A, ANT_B inverted) */
/*bResult &= BBbWriteEmbedded(dwIoBase,0x0a,0x28);*/
/* Select VC1/VC2, CR215 = 0x02->0x06 */
- bResult &= BBbWriteEmbedded(dwIoBase, 0xd7, 0x06);
+ bResult &= BBbWriteEmbedded(priv, 0xd7, 0x06);
/* }} */

for (ii = 0; ii < CB_VT3253B0_AGC; ii++)
--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/