Re: (subset) [PATCH 0/9] ASoC: Intel: avs: Set of functional fixes

[Cezary Rojewski <cezary.rojewski@intel.com>]

On 2025-06-02 6:42 PM, Mark Brown wrote:
> On Fri, 30 May 2025 16:10:16 +0200, Cezary Rojewski wrote:
>> Medium range of fixes all avs-driver related. The most important fixes
>> lead the way:
>>
>> 1. For ASoC-hda codec driver, existing RPM manipulation in
>> hda_codec_probe_complete()'s error path is superfluous and leads to RPM
>> usage count underflow if the probe exists early e.g.: build-controls
>> operation fails.
>>
>> [...]
> 
> Applied to
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> 
> Thanks!
> 
> [1/9] ASoC: codecs: hda: Fix RPM usage count underflow
>        commit: ff0045de4ee0288dec683690f66f2f369b7d3466
> [2/9] ASoC: Intel: avs: Fix deadlock when the failing IPC is SET_D0IX
>        commit: 9ad1f3cd0d60444c69948854c7e50d2a61b63755
> [3/9] ASoC: Intel: avs: Fix PPLCxFMT calculation
>        commit: 347c8d6db7c9d65d93ef226849b273823f54eaea
> [4/9] ASoC: Intel: avs: Fix possible null-ptr-deref when initing hw
>        commit: 2f78724d4f0c665c83e202e3989d5333a2cb1036
> [5/9] ASoC: Intel: avs: Fix paths in MODULE_FIRMWARE hints
>        commit: 9e3285be55e6c0829e451b4a341e3059da47ec9d
> [6/9] ASoC: Intel: avs: Verify kcalloc() status when setting constraints
>        commit: 5f342aeee2724d31046172eb5caab8e0e8afd57d
> [7/9] ASoC: Intel: avs: Verify content returned by parse_int_array()
>        commit: 93e246b6769bdacb09cfff4ea0f00fe5ab4f0d7a
> [9/9] ASoC: Intel: avs: Include missing string.h
>        commit: 38b1befc7a35a475d90ec32bfbe319f4412880a1


I've just checked broonie/sound/for-next and it seems the status of the 
branch matches above - patch 8/9 is _missing_.

At the same time, I do not see any reply with reasoning behind skipping 
the patch. What can I do to help address that?

> 
> 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
>