linux-kernel - Re: [PATCH] regmap: Don't warn about cache only mode for devices with no cache

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: <165636198441.4094714.10382838559554694205.b4-ty@kernel.org>
Date:   Mon, 27 Jun 2022 21:33:04 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, broonie@...nel.org
Cc:     dongas86@...il.com
Subject: Re: [PATCH] regmap: Don't warn about cache only mode for devices with no cache

On Wed, 22 Jun 2022 18:17:23 +0100, Mark Brown wrote:
> For devices with no cache it can make sense to use cache only mode as a
> mechanism for trapping writes to hardware which is inaccessible but since
> no cache is equivalent to cache bypass we force such devices into bypass
> mode. This means that our check that bypass and cache only mode aren't both
> enabled simultanously is less sensible for devices without a cache so relax
> it.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: Don't warn about cache only mode for devices with no cache
      commit: 3d0afe9cf1ef871a71596f990d7d2e60cc0b8669

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