linux-kernel - Re: [PATCH v2] ASoC: simple-card: Fix up checks for HW param fixups

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: <166619461019.884966.4133490951229701907.b4-ty@kernel.org>
Date:   Wed, 19 Oct 2022 16:50:10 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Aidan MacDonald <aidanmacdonald.0x0@...il.com>, lgirdwood@...il.com
Cc:     tiwai@...e.com, alsa-devel@...a-project.org,
        kuninori.morimoto.gx@...esas.com, linux-kernel@...r.kernel.org,
        spujar@...dia.com, perex@...ex.cz
Subject: Re: [PATCH v2] ASoC: simple-card: Fix up checks for HW param fixups

On Wed, 19 Oct 2022 02:23:02 +0100, Aidan MacDonald wrote:
> The "convert-xxx" properties only have an effect for DPCM DAI links.
> A DAI link is only created as DPCM if the device tree requires it;
> part of this involves checking for the use of "convert-xxx" properties.
> 
> When the convert-sample-format property was added, the checks got out
> of sync. A DAI link that specified only convert-sample-format but did
> not pass any of the other DPCM checks would not go into DPCM mode and
> the convert-sample-format property would be silently ignored.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: simple-card: Fix up checks for HW param fixups
      commit: 32def55d237e8507d4eb8442628fc2e59a899ea0

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