Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752053AbaLUISI (ORCPT ); Sun, 21 Dec 2014 03:18:08 -0500 Received: from mail-pa0-f41.google.com ([209.85.220.41]:65266 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750886AbaLUISD (ORCPT ); Sun, 21 Dec 2014 03:18:03 -0500 Date: Sun, 21 Dec 2014 00:17:59 -0800 From: Jeremiah Mahler To: Eddie Kovsky Cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] staging: vt6655: fix sparse warning: argument type Message-ID: <20141221081759.GC10123@hudson.localdomain> Mail-Followup-To: Jeremiah Mahler , Eddie Kovsky , Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org References: <20141221052755.GA3984@athena> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141221052755.GA3984@athena> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Eddie, all, On Sat, Dec 20, 2014 at 10:27:55PM -0700, Eddie Kovsky wrote: > Fixes following warning generated by sparse: > > 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] *dwIoBase > > Compile tested on next-20141219. > > Signed-off-by: Eddie Kovsky > --- > 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++) [...] The change looks right. BBbWriteEmbedded use priv to get dwIoBase. And every other call to BBbWriteEmbedded uses the priv argument. dwIoBase = priv->PortOffset; So how did this mistake get in there? It looks like it was simply missed in commit 377f5bc00f7e1. All the ones before and after were changed, but not this one. Interestingly, if you go back to this commit and compile it, no error is generated unless you enable sparse checks. -- - Jeremiah Mahler -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/