[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <167826314024.381778.9401502729139366282.b4-ty@ti.com>
Date: Wed, 8 Mar 2023 02:12:50 -0600
From: Nishanth Menon <nm@...com>
To: Santosh Shilimkar <ssantosh@...nel.org>,
Keerthy <j-keerthy@...com>, Tony Lindgren <tony@...mide.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Miaoqian Lin <linmq006@...il.com>
CC: Nishanth Menon <nm@...com>
Subject: Re: [PATCH] soc: ti: pm33xx: Fix refcount leak in am33xx_pm_probe
Hi Miaoqian Lin,
On Fri, 06 Jan 2023 09:40:22 +0400, Miaoqian Lin wrote:
> wkup_m3_ipc_get() takes refcount, which should be freed by
> wkup_m3_ipc_put(). Add missing refcount release in the error paths.
>
>
I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!
[1/1] soc: ti: pm33xx: Fix refcount leak in am33xx_pm_probe
commit: 8f3c307b580a4a6425896007325bddefc36e8d91
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists