linux-kernel - Re: [PATCH] ASoC: fsl_xcvr: clear the channel status control memory

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: <176417886645.96001.9476091546839523665.b4-ty@kernel.org>
Date: Wed, 26 Nov 2025 17:41:06 +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] ASoC: fsl_xcvr: clear the channel status control
 memory

On Wed, 26 Nov 2025 14:45:09 +0800, Shengjiu Wang wrote:
> memset_io() writes memory byte by byte with __raw_writeb() on the arm
> platform if the size is word. but XCVR data RAM memory can't be accessed
> with byte address, so with memset_io() the channel status control memory
> is not really cleared, use writel_relaxed() instead.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: fsl_xcvr: clear the channel status control memory
      commit: 73b97d46dde64fa184d47865d4a532d818c3a007

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