From: Dan Carpenter <dan.carpenter@linaro.org>
To: Arun R Murthy <arun.r.murthy@intel.com>
Cc: "Chaitanya Kumar Borah" <chaitanya.kumar.borah@intel.com>,
"David Airlie" <airlied@gmail.com>,
dri-devel@lists.freedesktop.org,
"Harry Wentland" <harry.wentland@amd.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
linux-kernel@vger.kernel.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Simona Vetter" <simona@ffwll.ch>,
"Suraj Kandpal" <suraj.kandpal@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Xaver Hugl" <xaver.hugl@kde.org>,
"Zack Rusin" <zack.rusin@broadcom.com>
Subject: [PATCH 0/3] drm/plane: Fix a couple NULL vs error pointer bugs
Date: Tue, 19 Aug 2025 12:38:12 +0300 [thread overview]
Message-ID: <cover.1755591666.git.dan.carpenter@linaro.org> (raw)
These are a couple fixes for NULL vs error pointer mixups. I had sent
the one earlier, and it was Acked but we forgot to apply it.
Dan Carpenter (3):
drm/plane: Clean up 0 vs NULL issue
drm/plane: Fix IS_ERR() vs NULL checks in
drm_plane_create_hotspot_properties()
drm/plane: Fix IS_ERR() vs NULL bugs in __drm_universal_plane_init()
drivers/gpu/drm/drm_plane.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--
2.47.2
next reply other threads:[~2025-08-19 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 9:38 Dan Carpenter [this message]
2025-08-19 9:38 ` [PATCH 1/3] drm/plane: Clean up 0 vs NULL issue Dan Carpenter
2025-08-19 9:38 ` [PATCH 2/3] drm/plane: Fix IS_ERR() vs NULL checks in drm_plane_create_hotspot_properties() Dan Carpenter
2025-08-19 9:38 ` [PATCH 3/3] drm/plane: Fix IS_ERR() vs NULL bugs in __drm_universal_plane_init() Dan Carpenter
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=cover.1755591666.git.dan.carpenter@linaro.org \
--to=dan.carpenter@linaro.org \
--cc=airlied@gmail.com \
--cc=arun.r.murthy@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=suraj.kandpal@intel.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
--cc=xaver.hugl@kde.org \
--cc=zack.rusin@broadcom.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;
as well as URLs for NNTP newsgroup(s).