From: Greg KH <gregkh@linuxfoundation.org>
To: Rahul Sharma <black.hawk@163.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Alex Hung <alex.hung@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Aurabindo Pillai <aurabindo.pillai@amd.com>
Subject: Re: Re: [PATCH v6.1] drm/amd/display: Check dce_hwseq before dereferencing it
Date: Tue, 20 Jan 2026 12:06:50 +0100 [thread overview]
Message-ID: <2026012033-jelly-hunger-fed8@gregkh> (raw)
In-Reply-To: <52c400f8.2ab6.19bc4bce26e.Coremail.black.hawk@163.com>
On Fri, Jan 16, 2026 at 10:57:51AM +0800, Rahul Sharma wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2026-01-15 19:44:04, "Greg KH" <gregkh@linuxfoundation.org> wrote:
> >On Thu, Jan 15, 2026 at 12:19:19PM +0800, Rahul Sharma wrote:
> >> From: Alex Hung <alex.hung@amd.com>
> >>
> >> [ Upstream b669507b637eb6b1aaecf347f193efccc65d756e commit ]
> >>
> >> [WHAT]
> >>
> >> hws was checked for null earlier in dce110_blank_stream, indicating hws
> >> can be null, and should be checked whenever it is used.
> >>
> >> Cc: Mario Limonciello <mario.limonciello@amd.com>
> >> Cc: Alex Deucher <alexander.deucher@amd.com>
> >> Reviewed-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> >> Signed-off-by: Alex Hung <alex.hung@amd.com>
> >> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >> (cherry picked from commit 79db43611ff61280b6de58ce1305e0b2ecf675ad)
> >> Cc: stable@vger.kernel.org
> >> [ The context change is due to the commit 8e7b3f5435b3
> >> ("drm/amd/display: Add control flag to dc_stream_state to skip eDP BL off/link off")
> >> and the commit a8728dbb4ba2 ("drm/amd/display: Refactor edp power
> >> control") and the proper adoption is done. ]
> >> Signed-off-by: Rahul Sharma <black.hawk@163.com>
> >> ---
> >> drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> >We need 6.6.y backport first, before we can take this one, for obvious
> >reasons (i.e. you do not want to have a regression). Can you submit
> >that one first and then this again?
>
> >
> Thanks Greg, I have sent out the backported patch for 6.6.y.
Great, can you resend this one as well? It's long-gone from my mail
system.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-20 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 4:19 Rahul Sharma
2026-01-15 11:44 ` Greg KH
[not found] ` <52c400f8.2ab6.19bc4bce26e.Coremail.black.hawk@163.com>
2026-01-20 11:06 ` Greg KH [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=2026012033-jelly-hunger-fed8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=black.hawk@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=stable@vger.kernel.org \
/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®