linux-kernel - Re: [PATCH v3 0/2] Two bug fixes for tas5805m codec driver

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]

Message-Id: <167571944937.1296981.10882189914536189021.b4-ty@kernel.org>
Date:   Mon, 06 Feb 2023 21:37:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Daniel Beer <daniel.beer@...rinstitute.com>
Cc:     linux-kernel@...r.kernel.org, Andy Liu <andy-liu@...com>
Subject: Re: [PATCH v3 0/2] Two bug fixes for tas5805m codec driver

On Sat, 04 Feb 2023 20:55:26 +1300, Daniel Beer wrote:
> This pair of patches fixes two issues which crept in while revising the
> original submission, at a time when I no longer had access to test
> hardware.
> 
> The fixes here have been tested and verified on hardware.
> 
> Changes v2 -> v3:
>   - Resubmit with cover letter
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: tas5805m: rework to avoid scheduling while atomic.
      commit: 147323792693bf013f60dca160be1d32bd4d180a
[2/2] ASoC: tas5805m: add missing page switch.
      commit: e0576cd642ced1ac65370b4516b7be9f536a0498

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