From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ye.xingchen@zte.com.cn
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, jonas@kwiboo.se, jernej.skrabec@gmail.com,
airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: bridge: simple-bridge: Use dev_err_probe()
Date: Wed, 22 Mar 2023 11:06:16 +0200 [thread overview]
Message-ID: <20230322090616.GJ20234@pendragon.ideasonboard.com> (raw)
In-Reply-To: <202303221622511915615@zte.com.cn>
Hi Ye,
Thank you for the patch.
On Wed, Mar 22, 2023 at 04:22:51PM +0800, ye.xingchen@zte.com.cn wrote:
> From: Ye Xingchen <ye.xingchen@zte.com.cn>
>
> Replace the open-code with dev_err_probe() to simplify the code.
>
> Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/gpu/drm/bridge/simple-bridge.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/simple-bridge.c b/drivers/gpu/drm/bridge/simple-bridge.c
> index 5ede3e111096..d85d9ee463b8 100644
> --- a/drivers/gpu/drm/bridge/simple-bridge.c
> +++ b/drivers/gpu/drm/bridge/simple-bridge.c
> @@ -202,11 +202,9 @@ static int simple_bridge_probe(struct platform_device *pdev)
>
> sbridge->enable = devm_gpiod_get_optional(&pdev->dev, "enable",
> GPIOD_OUT_LOW);
> - if (IS_ERR(sbridge->enable)) {
> - if (PTR_ERR(sbridge->enable) != -EPROBE_DEFER)
> - dev_err(&pdev->dev, "Unable to retrieve enable GPIO\n");
> - return PTR_ERR(sbridge->enable);
> - }
> + if (IS_ERR(sbridge->enable))
> + return dev_err_probe(&pdev->dev, PTR_ERR(sbridge->enable),
> + "Unable to retrieve enable GPIO\n");
>
> /* Register the bridge. */
> sbridge->bridge.funcs = &simple_bridge_bridge_funcs;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-03-22 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 8:22 [PATCH] drm: bridge: simple-bridge: Use dev_err_probe() ye.xingchen
2023-03-22 9:06 ` Laurent Pinchart [this message]
2023-03-22 10:53 ` Neil Armstrong
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=20230322090616.GJ20234@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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=ye.xingchen@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