From: Cezary Rojewski <cezary.rojewski@intel.com>
To: songxiebing <songxiebing@kylinos.cn>
Cc: <linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"kernel test robot" <lkp@intel.com>, <tiwai@suse.com>,
<broonie@kernel.org>
Subject: Re: [PATCH v2] ASoC: intel: avs: Fix type mismatch in variable assignment
Date: Tue, 7 Apr 2026 21:12:17 +0200 [thread overview]
Message-ID: <f9af61cd-9687-4f01-9562-79de0c9feae4@intel.com> (raw)
In-Reply-To: <20260325021752.238203-1-songxiebing@kylinos.cn>
On 2026-03-25 3:17 AM, songxiebing wrote:
> The input parameter requirement for snd_pcm_format_physical_with is
> snd_pcm_format_t,but params->codec.format is __u32, resulting in a
> mismatch error:
>
> sparse warnings: (new ones prefixed by >>)
>>> sound/soc/intel/avs/probes.c:147:58: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted snd_pcm_format_t [usertype] format @@ got unsigned int [usertype] format @@
> sound/soc/intel/avs/probes.c:147:58: sparse: expected restricted snd_pcm_format_t [usertype] format
> sound/soc/intel/avs/probes.c:147:58: sparse: got unsigned int [usertype] format
>
> So here, the format is cast to snd_pcm_format_t.
>
> Signed-off-by: songxiebing <songxiebing@kylinos.cn>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512190032.hnwn9mCV-lkp@intel.com/
While I see that this just got merged, the signed-off tag shall be the
last. Other than that, looks good.
Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
prev parent reply other threads:[~2026-04-07 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 3:27 [PATCH] ASOC: avs: Fix a sparse warnings for incorrect type in argument songxiebing
2026-03-25 2:17 ` [PATCH v2] ASoC: intel: avs: Fix type mismatch in variable assignment songxiebing
2026-04-07 11:34 ` Mark Brown
2026-04-07 19:12 ` Cezary Rojewski [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=f9af61cd-9687-4f01-9562-79de0c9feae4@intel.com \
--to=cezary.rojewski@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=songxiebing@kylinos.cn \
--cc=tiwai@suse.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