[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169040305934.140086.11999495195860520544.b4-ty@kernel.org>
Date: Wed, 26 Jul 2023 21:24:19 +0100
From: Mark Brown <broonie@...nel.org>
To: Shengjiu Wang <shengjiu.wang@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Fabio Estevam <festevam@...il.com>,
Nicolin Chen <nicoleotsuka@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Herve Codina <herve.codina@...tlin.com>
Cc: alsa-devel@...a-project.org, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH 1/1] ASoC: fsl: fsl_qmc_audio: Fix snd_pcm_format_t
values handling
On Wed, 26 Jul 2023 18:16:20 +0200, Herve Codina wrote:
> Running sparse on fsl_qmc_audio (make C=1) raises the following warnings:
> fsl_qmc_audio.c:387:26: warning: restricted snd_pcm_format_t degrades to integer
> fsl_qmc_audio.c:389:59: warning: incorrect type in argument 1 (different base types)
> fsl_qmc_audio.c:389:59: expected restricted snd_pcm_format_t [usertype] format
> fsl_qmc_audio.c:389:59: got unsigned int [assigned] i
> fsl_qmc_audio.c:564:26: warning: restricted snd_pcm_format_t degrades to integer
> fsl_qmc_audio.c:569:50: warning: incorrect type in argument 1 (different base types)
> fsl_qmc_audio.c:569:50: expected restricted snd_pcm_format_t [usertype] format
> fsl_qmc_audio.c:569:50: got int [assigned] i
> fsl_qmc_audio.c:573:62: warning: incorrect type in argument 1 (different base types)
> fsl_qmc_audio.c:573:62: expected restricted snd_pcm_format_t [usertype] format
> fsl_qmc_audio.c:573:62: got int [assigned] i
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: fsl: fsl_qmc_audio: Fix snd_pcm_format_t values handling
commit: 5befe22b3eebd07b334b2917f6d14ce7ee4c8404
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists