[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164746295912.1220201.14496447901680691673.b4-ty@kernel.org>
Date: Wed, 16 Mar 2022 20:35:59 +0000
From: Mark Brown <broonie@...nel.org>
To: Rikard Falkeborn <rikard.falkeborn@...il.com>,
Bixuan Cui <cuibixuan@...wei.com>,
YC Hung <yc.hung@...iatek.com>, alsa-devel@...a-project.org,
Jaroslav Kysela <perex@...ex.cz>,
Trevor Wu <trevor.wu@...iatek.com>,
Miaoqian Lin <linmq006@...il.com>,
linux-kernel@...r.kernel.org, Tzung-Bi Shih <tzungbi@...gle.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Matthias Brugger <matthias.bgg@...il.com>,
Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: mediatek: mt8195: Fix error handling in mt8195_mt6359_rt1019_rt5682_dev_probe
On Wed, 16 Mar 2022 08:46:15 +0000, Miaoqian Lin wrote:
> The device_node pointer is returned by of_parse_phandle() with refcount
> incremented. We should use of_node_put() on it when done.
>
> This function only calls of_node_put() in the regular path.
> And it will cause refcount leak in error path.
>
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: mediatek: mt8195: Fix error handling in mt8195_mt6359_rt1019_rt5682_dev_probe
commit: c4b7174fe5bb875a09a78674a14a1589d1a672f3
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