All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eslam Khafagy <eslam.medhat1993@gmail.com>
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: harry.wentland@amd.com, sunpeng.li@amd.com,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	airlied@linux.ie, daniel@ffwll.ch, mario.kleiner.de@gmail.com,
	hersenxs.wu@amd.com, Igor.A.Artemiev@mcst.ru,
	nikola.cornij@amd.com, srinivasan.shanmugam@amd.com,
	roman.li@amd.com, amd-gfx@lists.freedesktop.org,
	eslam.medhat1993@gmail.com
Subject: [PATCH 5.10.y 0/2] drm/amd/display: Fix potential null dereference
Date: Thu,  9 Oct 2025 05:17:10 +0300	[thread overview]
Message-ID: <cover.1759974167.git.eslam.medhat1993@gmail.com> (raw)

This series backports commit [52f1783ff414 ("drm/amd/display: Fix potential null dereference")]
to stable branch 5.10.y. However to apply this i had to backport commit
[3beac533b8da ("drm/amd/display: Remove redundant safeguards for dmub-srv destroy()")] first.

Igor Artemiev (1):
  drm/amd/display: Fix potential null dereference

Roman Li (1):
  drm/amd/display: Remove redundant safeguards for dmub-srv destroy()

 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

--
2.43.0


             reply	other threads:[~2025-10-09  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09  2:17 Eslam Khafagy [this message]
2025-10-09  2:17 ` [PATCH 5.10.y 1/2] drm/amd/display: Remove redundant safeguards for dmub-srv destroy() Eslam Khafagy
2025-10-09  2:17 ` [PATCH 5.10.y 2/2] drm/amd/display: Fix potential null dereference Eslam Khafagy

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.1759974167.git.eslam.medhat1993@gmail.com \
    --to=eslam.medhat1993@gmail.com \
    --cc=Igor.A.Artemiev@mcst.ru \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=harry.wentland@amd.com \
    --cc=hersenxs.wu@amd.com \
    --cc=mario.kleiner.de@gmail.com \
    --cc=nikola.cornij@amd.com \
    --cc=roman.li@amd.com \
    --cc=sashal@kernel.org \
    --cc=srinivasan.shanmugam@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=sunpeng.li@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.