This series fixes a bad guard conversion in one of the Qualcomm drivers.

Included is also a related cleanup.

Johan


Johan Hovold (2):
  ASoc: qcom: q6afe: fix bad guard conversion
  ASoc: qcom: q6afe: use guards consistently

 sound/soc/qcom/qdsp6/q6afe.c | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

-- 
2.51.2

On Wed, 03 Dec 2025 11:55:40 +0100, Johan Hovold wrote:
> This series fixes a bad guard conversion in one of the Qualcomm drivers.
> 
> Included is also a related cleanup.
> 
> Johan
> 
> 
> [...]

Applied to

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

Thanks!

[2/2] ASoc: qcom: q6afe: use guards consistently
      commit: dfbbd3c04f0f782e83f8677749e2f02359ffd1b5

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

On Wed, 03 Dec 2025 11:55:40 +0100, Johan Hovold wrote:
> This series fixes a bad guard conversion in one of the Qualcomm drivers.
> 
> Included is also a related cleanup.
> 
> Johan
> 
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoc: qcom: q6afe: fix bad guard conversion
      commit: 39191ce5dbfd65fededb4f0d408d6232c45766ba

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