linux-kernel - Re: [PATCH v2] regmap: sdw-mbq: Reorder regmap_mbq

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: <176254317709.12269.17989872302995356094.b4-ty@kernel.org>
Date: Fri, 07 Nov 2025 19:19:37 +0000
From: Mark Brown <broonie@...nel.org>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH v2] regmap: sdw-mbq: Reorder regmap_mbq_context struct
 for better packing

On Fri, 07 Nov 2025 10:45:51 +0000, Charles Keepax wrote:
> Avoid a hole in struct regmap_mbq_context by shuffling the members
> slightly. Pahole before:
> 
> struct regmap_mbq_context {
>         struct device *            dev;                  /*     0     8 */
>         struct sdw_slave *         sdw;                  /*     8     8 */
>         struct regmap_sdw_mbq_cfg  cfg;                  /*    16    32 */
>         int                        val_size;             /*    48     4 */
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: sdw-mbq: Reorder regmap_mbq_context struct for better packing
      commit: 6985defd1d832f1dd9d1977a6a2cc2cef7632704

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