From: Greg KH <gregkh@linuxfoundation.org>
To: Purva Yeshi <purvayeshi550@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] char: mwave: smapi: Fix signedness of SmapiOK variable
Date: Thu, 17 Apr 2025 11:38:06 +0200 [thread overview]
Message-ID: <2025041728-calamity-unsuited-4ba9@gregkh> (raw)
In-Reply-To: <20250417091018.29767-1-purvayeshi550@gmail.com>
On Thu, Apr 17, 2025 at 02:40:18PM +0530, Purva Yeshi wrote:
> Smatch warning:
> drivers/char/mwave/smapi.c:69 smapi_request() warn:
> assigning (-5) to unsigned variable 'usSmapiOK'
>
> Fix Smatch warning caused by assigning -EIO to an unsigned short.
>
> Smatch detected a warning due to assigning -EIO (a negative value) to an
> unsigned short variable, causing a type mismatch and potential issues.
>
> In v1, the type was changed to short, which resolved the warning, but
> retained the misleading "us" prefix in the variable name.
>
> In v2, update the type to s16 and rename the variable to SmapiOK,
> removing the "us" (unsigned short) prefix as per Greg KH suggestion.
>
> This change ensures type correctness, avoids confusion, and improves
> overall code readability.
>
> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
> ---
> V1 - https://lore.kernel.org/all/20250409211929.213360-1-purvayeshi550@gmail.com/
> V2 - Use s16 type and rename variable to remove misleading "us" prefix.
>
> drivers/char/mwave/smapi.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/char/mwave/smapi.c b/drivers/char/mwave/smapi.c
> index f8d79d393b69..65bc7e1ea6cf 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;
> + s16 SmapiOK = -EIO, *pSmapiOK = &SmapiOK;
Do you think that "SmapiOK" is a valid kernel variable name? Doesn't
look ok to me, what does checkpatch.pl say? :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-17 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 9:10 Purva Yeshi
2025-04-17 9:38 ` Greg KH [this message]
2025-04-17 9:49 ` Purva Yeshi
2025-04-17 10:19 ` Greg KH
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=2025041728-calamity-unsuited-4ba9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=purvayeshi550@gmail.com \
/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
all inboxes | Powered by JetHome®