From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: shao.mingyin@zte.com.cn
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, jonas@kwiboo.se, jernej.skrabec@gmail.com,
yang.yang29@zte.com.cn, xu.xin16@zte.com.cn,
ye.xingchen@zte.com.cn, linux-kernel@vger.kernel.org,
zhang.enpei@zte.com.cn
Subject: Re: [PATCH v2] drm/bridge: thc63lvd1024: Use dev_err_probe()
Date: Thu, 27 Mar 2025 10:44:53 +0200 [thread overview]
Message-ID: <20250327084453.GA4861@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20250327115249185_vgGyzfhDZjf43eXFwKqX@zte.com.cn>
Hi Zhang and Shao,
On Thu, Mar 27, 2025 at 11:52:49AM +0800, shao.mingyin@zte.com.cn wrote:
> From: Zhang Enpei <zhang.enpei@zte.com.cn>
>
> Replace the open-code with dev_err_probe() to simplify the code.
>
> Signed-off-by: Zhang Enpei <zhang.enpei@zte.com.cn>
> Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>
Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> v2:
> - reduce a PTR_ERR call since dev_err_probe() will add
> the error value to the message
> drivers/gpu/drm/bridge/thc63lvd1024.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c b/drivers/gpu/drm/bridge/thc63lvd1024.c
> index bba10cf9b4f9..8f3096fa3dd7 100644
> --- a/drivers/gpu/drm/bridge/thc63lvd1024.c
> +++ b/drivers/gpu/drm/bridge/thc63lvd1024.c
> @@ -188,14 +188,9 @@ static int thc63_probe(struct platform_device *pdev)
> platform_set_drvdata(pdev, thc63);
>
> thc63->vcc = devm_regulator_get(thc63->dev, "vcc");
> - if (IS_ERR(thc63->vcc)) {
> - if (PTR_ERR(thc63->vcc) == -EPROBE_DEFER)
> - return -EPROBE_DEFER;
> -
> - dev_err(thc63->dev, "Unable to get \"vcc\" supply: %ld\n",
> - PTR_ERR(thc63->vcc));
> - return PTR_ERR(thc63->vcc);
> - }
> + if (IS_ERR(thc63->vcc))
> + return dev_err_probe(thc63->dev, PTR_ERR(thc63->vcc),
> + "Unable to get \"vcc\" supply\n");
>
> ret = thc63_gpio_init(thc63);
> if (ret)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2025-03-27 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 3:52 shao.mingyin
2025-03-27 8:44 ` Laurent Pinchart [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=20250327084453.GA4861@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=ye.xingchen@zte.com.cn \
--cc=zhang.enpei@zte.com.cn \
/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
all inboxes | Powered by JetHome®