linux-kernel - Re: [PATCH] ASoC: cs35l56: Remove default from IRQ1

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]

Date: Fri, 09 Feb 2024 20:48:51 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Remove default from IRQ1_CFG register

On Fri, 09 Feb 2024 14:57:00 +0000, Richard Fitzgerald wrote:
> The driver never uses the IRQ1_CFG register so there's no need to provide
> a default value. It's set as a readable register only for debugging
> through the regmap registers file.
> 
> A system-specific firmware could overwrite this register with a non-default
> value. Therefore the driver can't hardcode what the initial value actually
> is. As the register is only for debugging the value can be left unknown
> until someone wants to read it through debugfs.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Remove default from IRQ1_CFG register
      commit: 727b943263dc98a7aca355cc0302158218f71543

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