linux-kernel - Re: [PATCH 1/2] regmap: ram: support noinc semantics

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: <169988434652.3280981.12852638097343584206.b4-ty@kernel.org>
Date:   Mon, 13 Nov 2023 14:05:46 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Ben Wolsieffer <ben.wolsieffer@...ring.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH 1/2] regmap: ram: support noinc semantics

On Thu, 02 Nov 2023 16:30:38 -0400, Ben Wolsieffer wrote:
> Support noinc semantics in RAM backed regmaps, for testing purposes. Add
> a new callback that selects registers which should have noinc behavior.
> Bulk writes to a noinc register will cause the last value in the buffer
> to be assigned to the register, while bulk reads will copy the same
> value repeatedly into the buffer.
> 
> This patch only adds support to regmap-raw-ram, since regmap-ram does
> not support bulk operations.
> 
> [...]

Applied to

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

Thanks!

[1/2] regmap: ram: support noinc semantics
      commit: 02e3564a344064aca49f147e8a4eecbe5d3459fc
[2/2] regmap: kunit: add noinc write test
      commit: d958d97848a6604d024221920d300d07869715a2

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