linux-kernel - Re: [PATCH] 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <167639771249.3067854.8958372042708188891.b4-ty@kernel.org>
Date:   Tue, 14 Feb 2023 18:01:52 +0000
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] regmap: Reorder fields in 'struct regmap_bus' to save
 some memory

On Tue, 14 Feb 2023 09:40:14 +0100, Christophe JAILLET wrote:
> Group some bool variables to reduce hole and avoid padding.
> On x86_64, this shrinks the size from 136 to 128 bytes.
> 
> As an example:
> 
> $ size drivers/base/regmap/regmap-fsi.o (Before)
>    text	   data	    bss	    dec	    hex	filename
>    4837	    136	      0	   4973	   136d	drivers/base/regmap/regmap-fsi.o
> 
> [...]

Applied to

   broonie/regmap.git for-next

Thanks!

[1/1] regmap: Reorder fields in 'struct regmap_bus' to save some memory
      commit: 7464145862d606cf9835f24080341a397cbc0669

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