From: Dragan Simic <dsimic@manjaro.org>
To: linux-rockchip@lists.infradead.org, linux-phy@lists.infradead.org
Cc: vkoul@kernel.org, kishon@kernel.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Improve error handling in Rockchip Inno USB 2.0 PHY driver
Date: Fri, 04 Oct 2024 08:46:19 +0200 [thread overview]
Message-ID: <71569a2773d88d13ca1cf4aa41b56496@manjaro.org> (raw)
In-Reply-To: <cover.1725524802.git.dsimic@manjaro.org>
Hello,
On 2024-09-05 10:28, Dragan Simic wrote:
> This is a small series that improves error handling in the probe path
> of the Rockchip Innosilicon USB 2.0 PHY driver, by returning the actual
> error code in one place and by using dev_err_probe() properly in
> multiple
> places. It also performs a bunch of small, rather trivial code
> cleanups,
> to make the code neater and a bit easier to read.
Just a brief reminder about this patch series... Please let me know
if something more is needed for these patches to be merged.
> Changes in v3:
> - Collected Reviewed-by tags from Heiko for patches 1/3 and 2/3
> - Brought back one empty line as a separator of dissimilar operations
> in patch 1/3, as suggested by Heiko [2]
> - Dropped one backward conversion of dev_err_probe() to dev_err() in
> patch 3/3, as suggested by Heiko, [3] and adjusted the summary and
> description of patch 3/3 accordingly
>
> Changes in v2:
> - Expanded into a small series, after a suggestion from Heiko [1] to
> use dev_err_probe(), because it all happens in the probe path
>
> Link to v2:
> https://lore.kernel.org/linux-phy/cover.1724225528.git.dsimic@manjaro.org/T/#u
> Link to v1:
> https://lore.kernel.org/linux-phy/5fa7796d71e2f46344e972bc98a54539f55b6109.1723551599.git.dsimic@manjaro.org/T/#u
>
> [1] https://lore.kernel.org/linux-phy/4927264.xgNZFEDtJV@diego/
> [2] https://lore.kernel.org/linux-phy/5307900.6fTUFtlzNn@diego/
> [3] https://lore.kernel.org/linux-phy/6073817.31tnzDBltd@diego/
>
> Dragan Simic (3):
> phy: phy-rockchip-inno-usb2: Perform trivial code cleanups
> phy: phy-rockchip-inno-usb2: Handle failed extcon allocation better
> phy: phy-rockchip-inno-usb2: Use dev_err_probe() in the probe path
>
> drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 56 +++++++------------
> 1 file changed, 21 insertions(+), 35 deletions(-)
next prev parent reply other threads:[~2024-10-04 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:28 [PATCH v3 0/3] Improve error handling in Rockchip Inno USB 2.0 PHY driver Dragan Simic
2024-09-05 8:28 ` [PATCH v3 1/3] phy: phy-rockchip-inno-usb2: Perform trivial code cleanups Dragan Simic
2024-09-05 8:28 ` [PATCH v3 2/3] phy: phy-rockchip-inno-usb2: Handle failed extcon allocation better Dragan Simic
2024-09-05 8:28 ` [PATCH v3 3/3] phy: phy-rockchip-inno-usb2: Use dev_err_probe() in the probe path Dragan Simic
2024-09-05 9:16 ` Heiko Stübner
2024-10-04 6:46 ` Dragan Simic [this message]
2024-10-07 15:48 ` [PATCH v3 0/3] Improve error handling in Rockchip Inno USB 2.0 PHY driver 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=71569a2773d88d13ca1cf4aa41b56496@manjaro.org \
--to=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).