From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Andy Gross <agross@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qcom-qmp: Make use of the helper function devm_add_action_or_reset()
Date: Wed, 22 Sep 2021 08:57:43 -0700 [thread overview]
Message-ID: <YUtSd7QxkSC0vPAa@ripper> (raw)
In-Reply-To: <20210922130017.692-1-caihuoqing@baidu.com>
On Wed 22 Sep 06:00 PDT 2021, Cai Huoqing wrote:
> The helper function devm_add_action_or_reset() will internally
> call devm_add_action(), and gif devm_add_action() fails then it will
> execute the action mentioned and return the error code. So
> use devm_add_action_or_reset() instead of devm_add_action()
> to simplify the error handling, reduce the code.
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
> drivers/phy/qualcomm/phy-qcom-qmp.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c
> index f14032170b1c..084e3d96264e 100644
> --- a/drivers/phy/qualcomm/phy-qcom-qmp.c
> +++ b/drivers/phy/qualcomm/phy-qcom-qmp.c
> @@ -5154,11 +5154,7 @@ static int phy_pipe_clk_register(struct qcom_qmp *qmp, struct device_node *np)
> * Roll a devm action because the clock provider is the child node, but
> * the child node is not actually a device.
> */
> - ret = devm_add_action(qmp->dev, phy_clk_release_provider, np);
> - if (ret)
> - phy_clk_release_provider(np);
> -
> - return ret;
> + return devm_add_action_or_reset(qmp->dev, phy_clk_release_provider, np);
> }
>
> /*
> @@ -5350,11 +5346,7 @@ static int phy_dp_clks_register(struct qcom_qmp *qmp, struct qmp_phy *qphy,
> * Roll a devm action because the clock provider is the child node, but
> * the child node is not actually a device.
> */
> - ret = devm_add_action(qmp->dev, phy_clk_release_provider, np);
> - if (ret)
> - phy_clk_release_provider(np);
> -
> - return ret;
> + return devm_add_action_or_reset(qmp->dev, phy_clk_release_provider, np);
> }
>
> static const struct phy_ops qcom_qmp_phy_gen_ops = {
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Andy Gross <agross@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qcom-qmp: Make use of the helper function devm_add_action_or_reset()
Date: Wed, 22 Sep 2021 08:57:43 -0700 [thread overview]
Message-ID: <YUtSd7QxkSC0vPAa@ripper> (raw)
In-Reply-To: <20210922130017.692-1-caihuoqing@baidu.com>
On Wed 22 Sep 06:00 PDT 2021, Cai Huoqing wrote:
> The helper function devm_add_action_or_reset() will internally
> call devm_add_action(), and gif devm_add_action() fails then it will
> execute the action mentioned and return the error code. So
> use devm_add_action_or_reset() instead of devm_add_action()
> to simplify the error handling, reduce the code.
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
> drivers/phy/qualcomm/phy-qcom-qmp.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c
> index f14032170b1c..084e3d96264e 100644
> --- a/drivers/phy/qualcomm/phy-qcom-qmp.c
> +++ b/drivers/phy/qualcomm/phy-qcom-qmp.c
> @@ -5154,11 +5154,7 @@ static int phy_pipe_clk_register(struct qcom_qmp *qmp, struct device_node *np)
> * Roll a devm action because the clock provider is the child node, but
> * the child node is not actually a device.
> */
> - ret = devm_add_action(qmp->dev, phy_clk_release_provider, np);
> - if (ret)
> - phy_clk_release_provider(np);
> -
> - return ret;
> + return devm_add_action_or_reset(qmp->dev, phy_clk_release_provider, np);
> }
>
> /*
> @@ -5350,11 +5346,7 @@ static int phy_dp_clks_register(struct qcom_qmp *qmp, struct qmp_phy *qphy,
> * Roll a devm action because the clock provider is the child node, but
> * the child node is not actually a device.
> */
> - ret = devm_add_action(qmp->dev, phy_clk_release_provider, np);
> - if (ret)
> - phy_clk_release_provider(np);
> -
> - return ret;
> + return devm_add_action_or_reset(qmp->dev, phy_clk_release_provider, np);
> }
>
> static const struct phy_ops qcom_qmp_phy_gen_ops = {
> --
> 2.25.1
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-09-22 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 13:00 [PATCH] phy: qcom-qmp: Make use of the helper function devm_add_action_or_reset() Cai Huoqing
2021-09-22 13:00 ` Cai Huoqing
2021-09-22 15:57 ` Bjorn Andersson [this message]
2021-09-22 15:57 ` Bjorn Andersson
2021-10-01 10:21 ` Vinod Koul
2021-10-01 10:21 ` 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=YUtSd7QxkSC0vPAa@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=caihuoqing@baidu.com \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.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.