linux-kernel - Re: [PATCH 0/2] ASoC: fsl: correct the bit order issue for DSD

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: <176156862139.24382.1000390767821381636.b4-ty@kernel.org>
Date: Mon, 27 Oct 2025 12:37:01 +0000
From: Mark Brown <broonie@...nel.org>
To: shengjiu.wang@...il.com, Xiubo.Lee@...il.com, festevam@...il.com, 
 nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-sound@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-kernel@...r.kernel.org, Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH 0/2] ASoC: fsl: correct the bit order issue for DSD

On Thu, 23 Oct 2025 14:45:36 +0800, Shengjiu Wang wrote:
> The DSD little endian format requires the msb first, the previous
> understanding is not correct. The issue is found by testing with
> pipewire.
> 
> Shengjiu Wang (2):
>   ASoC: fsl_sai: fix bit order for DSD format
>   ASoC: fsl_micfil: correct the endian format for DSD
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_sai: fix bit order for DSD format
      commit: d9fbe5b0bf7e2d1e20d53e4e2274f9f61bdcca98
[2/2] ASoC: fsl_micfil: correct the endian format for DSD
      commit: ba3a5e1aeaa01ea67067d725710a839114214fc6

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