public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Priestley <tvboxspy@gmail.com>
To: Jeremiah Mahler <jmmahler@gmail.com>,
	Eddie Kovsky <ewk@edkovsky.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: fix sparse warning: argument type
Date: Sun, 21 Dec 2014 10:17:17 +0000	[thread overview]
Message-ID: <54969E2D.2070505@gmail.com> (raw)
In-Reply-To: <20141221081759.GC10123@hudson.localdomain>

On 21/12/14 08:17, Jeremiah Mahler wrote:
> 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] <asn:2>*dwIoBase
>>
>> Compile tested on next-20141219.
>>
>> Signed-off-by: Eddie Kovsky <ewk@edkovsky.org>
>> ---
>>   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.
Yes it was missed probably because it looks like it commented out.

Good catch Eddie.

As my device does not this baseband type I won't encounter the bug.

Greg, this needs to go into 3.19.

Thanks

Malcolm

>
> Interestingly, if you go back to this commit and compile it, no error
> is generated unless you enable sparse checks.
>


      reply	other threads:[~2014-12-21 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21  5:27 [PATCH] staging: vt6655: fix sparse warning: argument type Eddie Kovsky
2014-12-21  8:17 ` Jeremiah Mahler
2014-12-21 10:17   ` Malcolm Priestley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54969E2D.2070505@gmail.com \
    --to=tvboxspy@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ewk@edkovsky.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmmahler@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox