linux-kernel - Re: [PATCH] ASoC: ops: fix pointer types to be big-endian

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: <176781257959.127389.8591799726303745547.b4-ty@kernel.org>
Date: Wed, 07 Jan 2026 19:02:59 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, Ben Dooks <ben.dooks@...ethink.co.uk>
Cc: lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: ops: fix pointer types to be big-endian

On Tue, 06 Jan 2026 22:58:46 +0000, Ben Dooks wrote:
> If manipulating big-endian data, make the pointers be big-endian
> instead of host-endian. This should stop the following sparse
> warnigns about endian-conversion:
> 
> sound/soc/soc-ops.c:547:33: warning: invalid assignment: &=
> sound/soc/soc-ops.c:547:33:    left side has type unsigned short
> sound/soc/soc-ops.c:547:33:    right side has type restricted __be16
> sound/soc/soc-ops.c:551:33: warning: invalid assignment: &=
> sound/soc/soc-ops.c:551:33:    left side has type unsigned int
> sound/soc/soc-ops.c:551:33:    right side has type restricted __be32
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: ops: fix pointer types to be big-endian
      commit: 2fa0eaf78c4bb24c2b05a4db3e0d86a7dcd8fd9f

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