linux-kernel - Re: [RESEND PATCH v2] ASoC: tegra: Fix DSPK 16-bit playback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 09 Apr 2024 14:07:50 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, alsa-devel@...a-project.org, 
 Sameer Pujar <spujar@...dia.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
 lgirdwood@...il.com, thierry.reding@...il.com, jonathanh@...dia.com, 
 mkumard@...dia.com, stable@...r.kernel.org
Subject: Re: [RESEND PATCH v2] ASoC: tegra: Fix DSPK 16-bit playback

On Fri, 05 Apr 2024 10:43:06 +0000, Sameer Pujar wrote:
> DSPK configuration is wrong for 16-bit playback and this happens because
> the client config is always fixed at 24-bit in hw_params(). Fix this by
> updating the client config to 16-bit for the respective playback.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tegra: Fix DSPK 16-bit playback
      commit: 2e93a29b48a017c777d4fcbfcc51aba4e6a90d38

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