From: Liu Ying <victor.liu@nxp.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
qijian.guo@nxp.com
Subject: Re: [PATCH] drm/bridge: waveshare-dsi: Fix bailout for devm_drm_bridge_alloc()
Date: Thu, 18 Sep 2025 14:02:34 +0800 [thread overview]
Message-ID: <cb6dd5ca-f5ae-4acb-8154-d9725ea80ce4@nxp.com> (raw)
In-Reply-To: <342ce13e-0c6d-43b8-a4fa-e9b29c0f8f96@nxp.com>
On 09/05/2025, Liu Ying wrote:
> On 8/6/25 16:41, Liu Ying wrote:
>> devm_drm_bridge_alloc() returns ERR_PTR on failure instead of a
>> NULL pointer, so use IS_ERR() to check the returned pointer and
>> turn proper error code on failure by using PTR_ERR().
>>
>> Fixes: dbdea37add13 ("drm: bridge: Add waveshare DSI2DPI unit driver")
>> Signed-off-by: Liu Ying <victor.liu@nxp.com>
>> ---
>> drivers/gpu/drm/bridge/waveshare-dsi.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Gentle ping for review.
Ping again.
>
>>
>> diff --git a/drivers/gpu/drm/bridge/waveshare-dsi.c b/drivers/gpu/drm/bridge/waveshare-dsi.c
>> index 01c70e7d3d3b..43f4e7412d72 100644
>> --- a/drivers/gpu/drm/bridge/waveshare-dsi.c
>> +++ b/drivers/gpu/drm/bridge/waveshare-dsi.c
>> @@ -147,8 +147,8 @@ static int ws_bridge_probe(struct i2c_client *i2c)
>> int ret;
>>
>> ws = devm_drm_bridge_alloc(dev, struct ws_bridge, bridge, &ws_bridge_bridge_funcs);
>> - if (!ws)
>> - return -ENOMEM;
>> + if (IS_ERR(ws))
>> + return PTR_ERR(ws);
>>
>> ws->dev = dev;
>>
>
--
Regards,
Liu Ying
next prev parent reply other threads:[~2025-09-18 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:41 Liu Ying
2025-09-05 8:40 ` Liu Ying
2025-09-18 6:02 ` Liu Ying [this message]
2025-09-18 12:44 ` Dmitry Baryshkov
2025-09-19 3:06 ` Liu Ying
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=cb6dd5ca-f5ae-4acb-8154-d9725ea80ce4@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=qijian.guo@nxp.com \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®