From: Vinod Koul <vkoul@kernel.org>
To: tomi.valkeinen@ideasonboard.com, neil.armstrong@linaro.org,
michal.simek@amd.com,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, git@amd.com
Subject: Re: [PATCH 0/2] phy: zynqmp: fix clock and runtime PM error paths in xpsgtr driver
Date: Wed, 22 Jul 2026 14:03:52 +0530 [thread overview]
Message-ID: <178470923263.211476.9299503935837490359.b4-ty@kernel.org> (raw)
In-Reply-To: <20260720153832.1130006-1-radhey.shyam.pandey@amd.com>
On Mon, 20 Jul 2026 21:08:29 +0530, Radhey Shyam Pandey wrote:
> This series fixes two pre-existing resource handling bugs in the Zynq
> UltraScale+ MPSoC Gigabit Transceiver (XPSGTR) PHY driver. They were
> reported during review of the SERDES scrambler series [1] and were
> intentionally deferred to this follow-up series.
>
> Patch 1:
> Propagate clk_prepare_enable() failures from xpsgtr_phy_init() and
> disable the reference clock on initialization error paths.
>
> [...]
Applied, thanks!
[1/2] phy: zynqmp: fix clock error handling in xpsgtr_phy_init()
commit: e4779e2a16d600892aaf743438f6ce8cc4eb3c4c
[2/2] phy: zynqmp: fix runtime PM leak on probe allocation failure
commit: f3506e15cf72e94f62d5f2d173e5b7008f644cde
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-07-22 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 15:38 [PATCH 0/2] phy: zynqmp: fix clock and runtime PM error paths in xpsgtr driver Radhey Shyam Pandey
2026-07-20 15:38 ` [PATCH 1/2] phy: zynqmp: fix clock error handling in xpsgtr_phy_init() Radhey Shyam Pandey
2026-07-21 5:39 ` Michal Simek
2026-07-20 15:38 ` [PATCH 2/2] phy: zynqmp: fix runtime PM leak on probe allocation failure Radhey Shyam Pandey
2026-07-20 15:57 ` sashiko-bot
2026-07-21 5:39 ` Michal Simek
2026-07-22 8:33 ` 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=178470923263.211476.9299503935837490359.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=git@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=michal.simek@amd.com \
--cc=neil.armstrong@linaro.org \
--cc=radhey.shyam.pandey@amd.com \
--cc=tomi.valkeinen@ideasonboard.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