linux-kernel - Re: [PATCH v1 0/3] regmap: Drop never (properly) worked 64-bit support

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:   Wed, 12 Jul 2023 12:47:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v1 0/3] regmap: Drop never (properly) worked 64-bit
 support

On Thu, 22 Jun 2023 21:36:10 +0300, Andy Shevchenko wrote:
> regmap API internally operates on unsigned int values for the register
> offsets and data. The commit back in 2015 that introduces 64-bit
> excerpts in the code made a false impression that it works. Not really.
> 
> Consider two things:
>  1/ register offset
>  2/ data
> 
> [...]

Applied to

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

Thanks!

[1/3] regmap: Revert "add 64-bit mode support" and Co.
      commit: 1425bdd7ef88631d0623ce3d0b8c89d8a65815d2
[2/3] regmap: cache: Revert "Add 64-bit mode support"
      commit: 039fd2e4134b7b880ba83f40a136df440047594a
[3/3] regmap: mmio: Remove unused 64-bit support code
      commit: 875403a7b524e9523e49dd32662adbc3e48cc12a

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