linux-kernel - Re: [PATCH] regmap: Support paging for buses with reg_read()/reg

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: <167992337653.3162264.89513525626078905.b4-ty@kernel.org>
Date:   Mon, 27 Mar 2023 14:22:56 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: Support paging for buses with
 reg_read()/reg_write()

On Fri, 24 Mar 2023 22:58:42 +0000, Mark Brown wrote:
> We don't currently support paging for regmaps where the I/O happens through
> bus provided reg_read() and reg_write() operatons, we simply ignore the
> range since nothing is wired up properly. Wire things up.
> 
> 

Applied to

   broonie/regmap.git for-next

Thanks!

[1/1] regmap: Support paging for buses with reg_read()/reg_write()
      commit: f18ee501e233a2b830a0c84a2e780ab02d946c04

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