From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: abdelnasser hussein <abdelnasserhussein11@gmail.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Mark Greer <mgreer@animalcreek.com>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] staging: greybus: audio: check sscanf() result directly
Date: Sun, 14 Jun 2026 08:15:58 +0200 [thread overview]
Message-ID: <2026061419-bunkmate-cinch-b506@gregkh> (raw)
In-Reply-To: <20260614060857.15366-1-abdelnasserhussein11@gmail.com>
On Sun, Jun 14, 2026 at 09:08:57AM +0300, abdelnasser hussein wrote:
> Smatch warns:
>
> drivers/staging/greybus/audio_codec.c:335 gbaudio_module_update()
> warn: sscanf doesn't return error codes
>
> sscanf() returns the number of successfully matched input items, not a
> negative error code. Compare the return value directly with the expected
> number of conversions instead of storing it in ret as an error code.
>
> Also remove the redundant else-if check for snd_soc_dapm_aif_out. The
> widget id is validated earlier in the function, so the remaining branch
> can only handle snd_soc_dapm_aif_out. This avoids a compiler warning
> about a potentially uninitialized variable.
When you say "also" that implies it should be a separate patch.
>
> Reported-by: kernel test robot <lkp@intel.com>
lkp didn't report the smatch warning :(
> Closes: https://lore.kernel.org/oe-kbuild-all/202606140347.gGVWDnbi-lkp@intel.com/
>
> Signed-off-by: abdelnasser hussein <abdelnasserhussein11@gmail.com>
> ---
> drivers/staging/greybus/audio_codec.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
No list of what changed from previous versions?
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-14 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 6:08 [PATCH v2] staging: greybus: audio: check sscanf() result directly abdelnasser hussein
2026-06-14 6:15 ` Greg Kroah-Hartman [this message]
2026-06-14 8:42 ` nasser
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=2026061419-bunkmate-cinch-b506@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abdelnasserhussein11@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=mgreer@animalcreek.com \
--cc=vaibhav.sr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.