mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "Chen Ni" <nichen@iscas.ac.cn>,
	dri-devel@lists.freedesktop.org,
	"Alex Lanzano" <lanzano.alex@gmail.com>,
	"David Airlie" <airlied@gmail.com>,
	"Dmitry Baryshkov" <lumag@kernel.org>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Mehdi Djait" <mehdi.djait@bootlin.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/sharp-memory: Fix IS_ERR() vs NULL check in sharp_memory_probe()
Date: Sat, 31 Jan 2026 08:04:38 +0100	[thread overview]
Message-ID: <7bfb2092-27da-4368-b95c-a57c11127651@web.de> (raw)
In-Reply-To: <20260130092300.3426214-1-nichen@iscas.ac.cn>

…
> Replace the NULL check after devm_drm_dev_alloc() with IS_ERR()

May extra error messages be omitted for selected allocation failures?



>                                                                 and add
> a missing IS_ERR() check after devm_gpiod_get_optional(). On error,
> return the error code from the probe function to ensure proper failure
> handling rather than proceeding with invalid pointers.

* Were any source code analysis tools involved here?

* Did anything hinder to add any tags (like “Fixes” and “Cc”) accordingly?


Regards,
Markus

      reply	other threads:[~2026-01-31  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  9:22 Chen Ni
2026-01-31  7:04 ` Markus Elfring [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=7bfb2092-27da-4368-b95c-a57c11127651@web.de \
    --to=markus.elfring@web.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lanzano.alex@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mehdi.djait@bootlin.com \
    --cc=mripard@kernel.org \
    --cc=nichen@iscas.ac.cn \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=u.kleine-koenig@baylibre.com \
    /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®