From: Abel Vesa <abel.vesa@linaro.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] phy: phy-snps-eusb2: fixes and cleanups
Date: Fri, 23 May 2025 11:57:48 +0300 [thread overview]
Message-ID: <aDA4jM0bb9kR7TiO@linaro.org> (raw)
In-Reply-To: <20250523084839.11015-1-johan+linaro@kernel.org>
On 25-05-23 10:48:32, Johan Hovold wrote:
> Here are a couple of fixes and some related cleanups to the recently
> reworked and renamed phy-snps-eusb2 driver.
>
> The clock and repeater imbalance fixes are not marked for stable as the
> first issue was introduced in the recent rework which is queued for
> 6.16-rc1.
>
> The repeater imbalance has been there for a few years and
> could be backported even if this is now complicated by the
> rework/rename. Since it only affects a resource leak in an error path I
> decided to not mark this one for stable for now.
>
> Ideally, these could go in along with the reworked driver for rc1.
>
> Johan
>
>
> Johan Hovold (7):
> phy: phy-snps-eusb2: fix clock imbalance on phy_exit()
> phy: phy-snps-eusb2: fix repeater imbalance on phy_init() failure
> phy: phy-snps-eusb2: rename phy_init() clock error label
> phy: phy-snps-eusb2: clean up error messages
> phy: phy-snps-eusb2: fix optional phy lookup parameter
> phy: phy-snps-eusb2: drop unnecessary loop index declarations
> phy: phy-snps-eusb2: clean up id table sentinel
Really straightforward. So for the entire series:
Reviewed-by: Abel Vesa <abel.vesa@linaro.org>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Abel Vesa <abel.vesa@linaro.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] phy: phy-snps-eusb2: fixes and cleanups
Date: Fri, 23 May 2025 11:57:48 +0300 [thread overview]
Message-ID: <aDA4jM0bb9kR7TiO@linaro.org> (raw)
In-Reply-To: <20250523084839.11015-1-johan+linaro@kernel.org>
On 25-05-23 10:48:32, Johan Hovold wrote:
> Here are a couple of fixes and some related cleanups to the recently
> reworked and renamed phy-snps-eusb2 driver.
>
> The clock and repeater imbalance fixes are not marked for stable as the
> first issue was introduced in the recent rework which is queued for
> 6.16-rc1.
>
> The repeater imbalance has been there for a few years and
> could be backported even if this is now complicated by the
> rework/rename. Since it only affects a resource leak in an error path I
> decided to not mark this one for stable for now.
>
> Ideally, these could go in along with the reworked driver for rc1.
>
> Johan
>
>
> Johan Hovold (7):
> phy: phy-snps-eusb2: fix clock imbalance on phy_exit()
> phy: phy-snps-eusb2: fix repeater imbalance on phy_init() failure
> phy: phy-snps-eusb2: rename phy_init() clock error label
> phy: phy-snps-eusb2: clean up error messages
> phy: phy-snps-eusb2: fix optional phy lookup parameter
> phy: phy-snps-eusb2: drop unnecessary loop index declarations
> phy: phy-snps-eusb2: clean up id table sentinel
Really straightforward. So for the entire series:
Reviewed-by: Abel Vesa <abel.vesa@linaro.org>
next prev parent reply other threads:[~2025-05-23 8:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 8:48 [PATCH 0/7] phy: phy-snps-eusb2: fixes and cleanups Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-23 8:48 ` [PATCH 1/7] phy: phy-snps-eusb2: fix clock imbalance on phy_exit() Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-25 13:17 ` Ivaylo Ivanov
2025-05-25 13:17 ` Ivaylo Ivanov
2025-05-26 7:49 ` neil.armstrong
2025-05-26 7:49 ` neil.armstrong
2025-05-23 8:48 ` [PATCH 2/7] phy: phy-snps-eusb2: fix repeater imbalance on phy_init() failure Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-26 7:49 ` Neil Armstrong
2025-05-26 7:49 ` Neil Armstrong
2025-05-23 8:48 ` [PATCH 3/7] phy: phy-snps-eusb2: rename phy_init() clock error label Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-26 7:49 ` neil.armstrong
2025-05-26 7:49 ` neil.armstrong
2025-05-23 8:48 ` [PATCH 4/7] phy: phy-snps-eusb2: clean up error messages Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-26 7:50 ` neil.armstrong
2025-05-26 7:50 ` neil.armstrong
2025-05-23 8:48 ` [PATCH 5/7] phy: phy-snps-eusb2: fix optional phy lookup parameter Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-26 8:27 ` neil.armstrong
2025-05-26 8:27 ` neil.armstrong
2025-05-23 8:48 ` [PATCH 6/7] phy: phy-snps-eusb2: drop unnecessary loop index declarations Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-26 8:27 ` neil.armstrong
2025-05-26 8:27 ` neil.armstrong
2025-05-23 8:48 ` [PATCH 7/7] phy: phy-snps-eusb2: clean up id table sentinel Johan Hovold
2025-05-23 8:48 ` Johan Hovold
2025-05-23 8:57 ` Abel Vesa [this message]
2025-05-23 8:57 ` [PATCH 0/7] phy: phy-snps-eusb2: fixes and cleanups Abel Vesa
2025-06-15 16:53 ` Vinod Koul
2025-06-15 16:53 ` Vinod Koul
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=aDA4jM0bb9kR7TiO@linaro.org \
--to=abel.vesa@linaro.org \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=vkoul@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.