[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174705176600.71095.8384606721205945217.b4-ty@kernel.org>
Date: Mon, 12 May 2025 21:09:26 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Varshini Rajendran <varshini.rajendran@...rochip.com>,
Tudor Ambarus <tudor.ambarus@...aro.org>, linux-spi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Bence Csókás <csokas.bence@...lan.hu>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Danilo Krummrich <dakr@...nel.org>, Alexander Dahl <ada@...rsis.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>
Subject: Re: [PATCH v6 0/2] Add more devm_ functions to fix PM imbalance in
spi/atmel-quadspi.c
On Thu, 27 Mar 2025 20:59:25 +0100, Bence Csókás wrote:
> The probe() function of the atmel-quadspi driver got quite convoluted,
> especially since the addition of SAMA7G5 support, that was forward-ported
> from an older vendor kernel. During the port, a bug was introduced, where
> the PM get() and put() calls were imbalanced. To alleivate this - and
> similar problems in the future - an effort was made to migrate as many
> functions as possible, to their devm_ managed counterparts. The few
> functions, which did not yet have a devm_ variant, are added in patch 1 of
> this series. Patch 2 then uses these APIs to fix the probe() function.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] pm: runtime: Add new devm functions
(no commit info)
[2/2] spi: atmel-quadspi: Fix unbalanced pm_runtime by using devm_ API
commit: 8856eafcc05ecf54d6dd2b6c67804fefd276472c
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
Powered by blists - more mailing lists