From: Vinod Koul <vkoul@kernel.org>
To: neil.armstrong@linaro.org, johan@kernel.org, kishon@kernel.org,
rogerq@ti.com, Hongling Zeng <zenghongling@kylinos.cn>
Cc: linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
zhongling0719@126.com
Subject: Re: [PATCH v8 0/4] phy: ti-pipe3: Fix clock resource handling issues
Date: Thu, 12 Nov 2026 14:33:41 +0530 [thread overview]
Message-ID: <179447422182.428158.17793904820702370114.b4-ty@kernel.org> (raw)
In-Reply-To: <20260909122630.1313205-1-zenghongling@kylinos.cn>
On Wed, 09 Sep 2026 20:26:26 +0800, Hongling Zeng wrote:
> This patch series fixes multiple clock resource handling issues in the
> ti-pipe3 PHY driver.
>
> Patch 1 fixes a critical issue where ti_pipe3_init() was ignoring the
> return value of ti_pipe3_enable_clocks(), which could lead to unclocked
> hardware access and unbalanced clock disables.
>
> [...]
Applied, thanks!
[1/4] phy: ti-pipe3: Fix ignored clock enable return value in init
commit: 64207b5bc6be7db5e75ba9b7eb271dbda30834e5
[2/4] phy: ti: pipe3: Fix clock resource leak on probe errors
commit: 6dc01e3516d79cf4d690d892499a0bd08a14285b
[3/4] phy: ti-pipe3: Fix EPROBE_DEFER handling for clock resources
commit: aeb637c73631851de0965514151f7ff7bc13f940
[4/4] phy: ti-pipe3: Fix clock leaks in init/exit error paths
commit: 2be6a65608a5e32b2be6f5da843b1f29f1091098
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-11-12 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:26 Hongling Zeng
2026-09-09 12:26 ` [PATCH v8 1/4] phy: ti-pipe3: Fix ignored clock enable return value in init Hongling Zeng
2026-09-09 12:26 ` [PATCH v8 2/4] phy: ti: pipe3: Fix clock resource leak on probe errors Hongling Zeng
2026-10-12 12:56 ` Manivannan Sadhasivam
2026-09-09 12:26 ` [PATCH v8 3/4] phy: ti-pipe3: Fix EPROBE_DEFER handling for clock resources Hongling Zeng
2026-10-12 12:59 ` Manivannan Sadhasivam
2026-09-09 12:26 ` [PATCH v8 4/4] phy: ti-pipe3: Fix clock leaks in init/exit error paths Hongling Zeng
2026-10-12 13:05 ` Manivannan Sadhasivam
2026-11-12 9:03 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179447422182.428158.17793904820702370114.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=rogerq@ti.com \
--cc=zenghongling@kylinos.cn \
--cc=zhongling0719@126.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®