From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 026C047CC61 for ; Wed, 22 Jul 2026 08:33:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784709240; cv=none; b=BMD1UxWCCAbbWN1I96P6PGpn4wGfcAetgNNT71VlMIUqKFcmFsN/zhoJkUNn3P0NdkNsvKUL2oy3wL1dt777tmF1AwsmH2YO6TAkIFVJagIMpkdmjhWpM4lPC4PDv+9F9Ftc7TdD9nt2gocX+nrv6V/4PPO4YEc62soRkWRTPxI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784709240; c=relaxed/simple; bh=vQi7xTiO53XrEPe9ootAZ5OX3/Mo2KoaA59nwwkTJI0=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=At9Ijjvh3NDWeKa7jTr6bQZpthNHeNTHc/qP1bV9+moNxcxdzC9bg2YA5t8ZA2LuGvBfN3T+qTJNbDtxGO8xu/HyBc/x0qLtAS/aElSgHc+Y4GUnCNyoXAiqZiG5+7AdjuDt2wO17DCTUJV+3igzNlM/+vcf3A3rG4FWPFKoWVs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KqoAGV41; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KqoAGV41" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 08D281F000E9; Wed, 22 Jul 2026 08:33:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784709235; bh=wtg9G2dp9qrHcHk+gGP2VMglqa7zLggUFlaPWcMwIKY=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=KqoAGV41PR28Cfy7PtbBSBNW8Zi/rKvmaPUxp1n1VfHcGnGdt38CTAHOEIfIY2ltk 1FiWFfC21E1Fcnj5i4t1lkbKrPwP3K2w2ghlsEiDy1cOA8O4b+C4mLYn1iP+OmkRTL M7wF4e+AYI0FvnZpgpSc4QrgiG1IqplhT8Oo9CliiZuWFgriR1arqW4bj+FNb/AIxH 6mN/UQaUK3zyIFHKrS0MBZlbWmrGVRGPt8z7jetS8WdFF8ZHf8Gfnp8mpeiVhVahgJ mLg1P5WyrPf+IeXfOtveLIvvFuZKLsEW/XOgthgJtFrVVYe7ZfpEM4tCu7aN3iCSnl TERg/lOA1cJUQ== From: Vinod Koul To: tomi.valkeinen@ideasonboard.com, neil.armstrong@linaro.org, michal.simek@amd.com, Radhey Shyam Pandey Cc: linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, git@amd.com In-Reply-To: <20260720153832.1130006-1-radhey.shyam.pandey@amd.com> References: <20260720153832.1130006-1-radhey.shyam.pandey@amd.com> Subject: Re: [PATCH 0/2] phy: zynqmp: fix clock and runtime PM error paths in xpsgtr driver Message-Id: <178470923263.211476.9299503935837490359.b4-ty@kernel.org> Date: Wed, 22 Jul 2026 14:03:52 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13.0 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