linux-kernel - Re: [PATCH] regmap: Clarify error for unknown cache types

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:   Mon, 27 Mar 2023 14:22:55 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: Clarify error for unknown cache types

On Fri, 24 Mar 2023 16:22:26 +0000, Mark Brown wrote:
> The error message printed when we fail to locate the cache type the map
> requested says it can't find a compress type rather than a cache type,
> fix that. Since the compressed type is the only one currently compiled
> conditionally it's likely to be the missing type but that might not always
> be true and is still unclear.
> 
> 
> [...]

Applied to

   broonie/regmap.git for-next

Thanks!

[1/1] regmap: Clarify error for unknown cache types
      commit: 2d38e8615a21e264042870f811247d5c52c27f4e

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