public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Purva Yeshi <purvayeshi550@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char: mwave: smapi: Make usSmapiOK signed to fix warning
Date: Thu, 17 Apr 2025 11:29:20 +0530	[thread overview]
Message-ID: <927ff3f8-8814-4f95-ab85-0e0c14c6ed85@gmail.com> (raw)
In-Reply-To: <2025041520-culinary-obsessive-1dc3@gregkh>

On 15/04/25 20:22, Greg KH wrote:
> On Thu, Apr 10, 2025 at 02:49:29AM +0530, Purva Yeshi wrote:
>> Fix Smatch-detected warning:
>> drivers/char/mwave/smapi.c:69 smapi_request() warn:
>> assigning (-5) to unsigned variable 'usSmapiOK'
>>
>> Assigning a negative value (-EIO, which is -5) to an unsigned short
>> (usSmapiOK) causes a Smatch warning because negative values cannot
>> be correctly represented in an unsigned type, leading to unexpected
>> behavior.
>>
>> Change the type of usSmapiOK from unsigned short to short to allow
>> storing negative values like -EIO without causing a type mismatch or
>> logic error.
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>> ---
>>   drivers/char/mwave/smapi.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/char/mwave/smapi.c b/drivers/char/mwave/smapi.c
>> index f8d79d393b69..37da1339357e 100644
>> --- a/drivers/char/mwave/smapi.c
>> +++ b/drivers/char/mwave/smapi.c
>> @@ -66,7 +66,7 @@ static int smapi_request(unsigned short inBX, unsigned short inCX,
>>   	unsigned short myoutDX = 5, *pmyoutDX = &myoutDX;
>>   	unsigned short myoutDI = 6, *pmyoutDI = &myoutDI;
>>   	unsigned short myoutSI = 7, *pmyoutSI = &myoutSI;
>> -	unsigned short usSmapiOK = -EIO, *pusSmapiOK = &usSmapiOK;
>> +	short usSmapiOK = -EIO, *pusSmapiOK = &usSmapiOK;
> 
> This no longer a "us" variable type :(
> 
> The joy of using this type of notation, ick.  Please fix this up to use
> an explicit type (like s16), and fix the variable name at the same time.
> 
> thanks,
> 
> greg k-h

Hi Greg,

Thanks for the feedback.

I’ll update the patch to use an explicit s16 type and rename the 
usSmapiOK with SmapiOK to match the new type. I’ll send a v2 shortly.

Best regards,
Purva

      reply	other threads:[~2025-04-17  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 21:19 [PATCH] char: mwave: smapi: Make usSmapiOK signed to fix warning Purva Yeshi
2025-04-15 14:52 ` Greg KH
2025-04-17  5:59   ` Purva Yeshi [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=927ff3f8-8814-4f95-ab85-0e0c14c6ed85@gmail.com \
    --to=purvayeshi550@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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