linux-kernel - Re: [PATCH] regmap: mmio: Allow passing an empty config->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: <168386516384.353123.11293244589798997385.b4-ty@kernel.org>
Date:   Fri, 12 May 2023 13:19:23 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        Colin Foster <colin.foster@...advantage.com>,
        Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc:     linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com,
        alexis.lothore@...tlin.com
Subject: Re: [PATCH] regmap: mmio: Allow passing an empty
 config->reg_stride

On Thu, 11 May 2023 16:27:35 +0200, Maxime Chevallier wrote:
> Regmap's stride is used for MMIO regmaps to check the correctness of
> reg_width. However, it's acceptable to pass an empty config->reg_stride,
> in that case the actual stride used is 1.
> 
> There are valid cases now to pass an empty stride, when using
> down/upshifting of register address. In this case, the stride value
> loses its sense, so ignore the reg_width when the stride isn't set.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: mmio: Allow passing an empty config->reg_stride
      commit: e12ff28764937dd58c8613f16065da60da149048

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