linux-kernel - Re: [PATCH] ASoC: cs35l45: Add endianness flag in snd_soc_component

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: <165522725660.2442209.5932511980580944240.b4-ty@kernel.org>
Date:   Tue, 14 Jun 2022 18:20:56 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        lgirdwood@...il.com, patches@...nsource.cirrus.com,
        james.schulman@...rus.com, david.rhodes@...rus.com
Subject: Re: [PATCH] ASoC: cs35l45: Add endianness flag in snd_soc_component_driver

On Tue, 14 Jun 2022 14:10:22 +0100, Charles Keepax wrote:
> The endianness flag is used on the CODEC side to specify an
> ambivalence to endian, typically because it is lost over the hardware
> link. This device receives audio over an I2S DAI and as such should
> have endianness applied.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: cs35l45: Add endianness flag in snd_soc_component_driver
      commit: d919630fe77904931277e663c902582ea6f4e4cf

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