linux-kernel - Re: [PATCH v1] ASoc: TAS2781: replace beXX_to_cpup with get_unaligned

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: <172044796258.45994.10321780261934158542.b4-ty@kernel.org>
Date: Mon, 08 Jul 2024 15:12:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 pierre-louis.bossart@...ux.intel.com, 13916275206@....com, 
 zhourui@...qin.com, alsa-devel@...a-project.org, i-salazar@...com, 
 linux-kernel@...r.kernel.org, j-chadha@...com, liam.r.girdwood@...el.com, 
 jaden-yue@...com, yung-chuan.liao@...ux.intel.com, dipa@...com, 
 yuhsuan@...gle.com, henry.lo@...com, tiwai@...e.de, baojun.xu@...com, 
 soyer@....hu, Baojun.Xu@....com, judyhsiao@...gle.com, navada@...com, 
 cujomalainey@...gle.com, aanya@...com, nayeem.mahmud@...com, 
 savyasanchi.shukla@...radyne.com, flaviopr@...rosoft.com, jesse-ji@...com, 
 darren.ye@...iatek.com
Subject: Re: [PATCH v1] ASoc: TAS2781: replace beXX_to_cpup with
 get_unaligned_beXX for potentially broken alignment

On Sun, 07 Jul 2024 16:30:07 +0800, Shenghao Ding wrote:
> Use get_unaligned_be16 instead of be16_to_cpup and get_unaligned_be32
> instead of be32_to_cpup for potentially broken alignment.
> 
> 

Applied to

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

Thanks!

[1/1] ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment
      commit: 1cc509edbe23b61e8c245611bd15d88edb635a38

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