linux-kernel - Re: [PATCH v2] regulator: ti-abb: don't use devm_platform_ioremap_resource

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: <170611989327.57373.13632353759859941930.b4-ty@kernel.org>
Date: Wed, 24 Jan 2024 18:11:33 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, 
 Romain Naour <romain.naour@...le.fr>
Cc: tony@...mide.com, lgirdwood@...il.com, 
 Romain Naour <romain.naour@....com>, Yoann Congal <yoann.congal@...le.fr>
Subject: Re: [PATCH v2] regulator: ti-abb: don't use
 devm_platform_ioremap_resource_byname for shared interrupt register

On Tue, 23 Jan 2024 12:14:56 +0100, Romain Naour wrote:
> We can't use devm_platform_ioremap_resource_byname() to remap the
> interrupt register that can be shared between
> regulator-abb-{ivahd,dspeve,gpu} drivers instances.
> 
> The combined helper introduce a call to devm_request_mem_region() that
> creates a new busy resource region on PRM_IRQSTATUS_MPU register
> (0x4ae06010). The first devm_request_mem_region() call succeeds for
> regulator-abb-ivahd but fails for the two other regulator-abb-dspeve
> and regulator-abb-gpu.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: ti-abb: don't use devm_platform_ioremap_resource_byname for shared interrupt register
      commit: a67e1f0bd4564b485e0f0c3ed7f6bf17688be268

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