linux-kernel - Re: [PATCH] regmap: fix bogus error on regcache

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: <170170736703.96972.10213325187917313129.b4-ty@kernel.org>
Date:   Mon, 04 Dec 2023 16:29:27 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Matthias Reichl <hias@...us.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: fix bogus error on regcache_sync success

On Sun, 03 Dec 2023 23:22:16 +0100, Matthias Reichl wrote:
> Since commit 0ec7731655de ("regmap: Ensure range selector registers
> are updated after cache sync") opening pcm512x based soundcards fail
> with EINVAL and dmesg shows sync cache and pm_runtime_get errors:
> 
> [  228.794676] pcm512x 1-004c: Failed to sync cache: -22
> [  228.794740] pcm512x 1-004c: ASoC: error at snd_soc_pcm_component_pm_runtime_get on pcm512x.1-004c: -22
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: fix bogus error on regcache_sync success
      commit: fea88064445a59584460f7f67d102b6e5fc1ca1d

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