linux-kernel - Re: [PATCH] regmap: Drop early readability check

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: <168692172278.235227.5361924639572805383.b4-ty@kernel.org>
Date:   Fri, 16 Jun 2023 14:22:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Konrad Dybcio <konradybcio@...nel.org>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: Drop early readability check

On Fri, 16 Jun 2023 00:04:40 +0100, Mark Brown wrote:
> We have some drivers that have a use case for cached write only
> registers, doing read/modify/writes on read only registers in order to
> work more easily with bitfields.  Go back to trying the cache before we
> check if we can read from the device.
> 
> 

Applied to

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

Thanks!

[1/1] regmap: Drop early readability check
      commit: 3e47b8877d6c0f60943b00f3112756ca3b572cd6

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