linux-kernel - Re: [PATCH 0/2] regmap: add const_struct.checkpatch entries and constify regmap_irq_sub_irq

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: <172044878853.64339.13835076848317107720.b4-ty@kernel.org>
Date: Mon, 08 Jul 2024 15:26:28 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@...nel.org>, 
 Thomas Weißschuh <linux@...ssschuh.net>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regmap: add const_struct.checkpatch entries and
 constify regmap_irq_sub_irq_map

On Sat, 06 Jul 2024 13:13:40 +0200, Thomas Weißschuh wrote:
> Some non-functional changes to enable more .rodata structs.
> 
> 

Applied to

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

Thanks!

[1/2] const_structs.checkpatch: add regmap structs
      commit: 0f02ba48cdaf482d6756515e6936c1e23a316eac
[2/2] regmap-irq: handle const struct regmap_irq_sub_irq_map
      commit: f21711bbdbf0d95a389bfaad54ce444b46830d58

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