linux-kernel - Re: [PATCH v1] regmap: Reorder fields in 'struct regmap

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <171509390823.1990981.2169918651206303551.b4-ty@kernel.org>
Date: Tue, 07 May 2024 23:58:28 +0900
From: Mark Brown <broonie@...nel.org>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v1] regmap: Reorder fields in 'struct regmap_config' to
 save some memory

On Mon, 06 May 2024 21:33:33 +0200, Christophe JAILLET wrote:
> On x86_64 and allmodconfig, this shrinks the size of 'struct regmap_config'
> from 328 to 312 bytes.
> 
> This is usually a win, because this structure is used as a static global
> variable.
> 
> When moving the kerneldoc fields, I've tried to keep the layout as
> consistent as possible, which is not really easy!
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: Reorder fields in 'struct regmap_config' to save some memory
      commit: 9b1fe0510494c989ab6a131ce8b97cdd02a1c869

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