[PATCH 0/3] ASoC: qcom: audioreach: fix sparse warnings

Srinivas Kandagatla posted 3 patches 1 month, 1 week ago
sound/soc/qcom/qdsp6/audioreach.c | 2 +-
sound/soc/qcom/qdsp6/topology.c   | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
[PATCH 0/3] ASoC: qcom: audioreach: fix sparse warnings
Posted by Srinivas Kandagatla 1 month, 1 week ago
Recent static calibration support patches have excersised new code path
exposing some missing checks and also accessing some variables which are 
of LE type that are accessed directly without converting it to CPU type.

Thanks to Dan Carpenter and kernel test robot for reporting this.

--srini

Srinivas Kandagatla (3):
  ASoC: qcom: audioreach: fix potential null pointer dereference
  ASoC: qcom: topology: convert to cpu endainess type before accessing
  ASoC: qcom: audioreach: convert to cpu endainess type before accessing

 sound/soc/qcom/qdsp6/audioreach.c | 2 +-
 sound/soc/qcom/qdsp6/topology.c   | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.50.0
Re: [PATCH 0/3] ASoC: qcom: audioreach: fix sparse warnings
Posted by Mark Brown 1 month ago
On Mon, 25 Aug 2025 11:12:44 +0100, Srinivas Kandagatla wrote:
> Recent static calibration support patches have excersised new code path
> exposing some missing checks and also accessing some variables which are
> of LE type that are accessed directly without converting it to CPU type.
> 
> Thanks to Dan Carpenter and kernel test robot for reporting this.
> 
> --srini
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: qcom: audioreach: fix potential null pointer dereference
      commit: 8318e04ab2526b155773313b66a1542476ce1106
[2/3] ASoC: qcom: topology: convert to cpu endainess type before accessing
      commit: 7e67e1c99efa6ecd003d51a42dbe7bd5bad329eb
[3/3] ASoC: qcom: audioreach: convert to cpu endainess type before accessing
      commit: 8f57dcf39fd0864f5f3e6701fe885e55f45d0d3a

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