From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Pananchikkal, Renjith" <Renjith.Pananchikkal@amd.com>
Subject: Re: A few HDMI fixes for 6.18.y
Date: Wed, 25 Feb 2026 06:23:52 -0800 [thread overview]
Message-ID: <2026022524-carbon-paltry-1db0@gregkh> (raw)
In-Reply-To: <c6996c83-db35-4f2c-b11d-dbb4eaeb7269@amd.com>
On Tue, Feb 24, 2026 at 08:31:06PM -0600, Mario Limonciello wrote:
>
>
> On 2/24/2026 6:56 PM, Greg KH wrote:
> > On Mon, Feb 23, 2026 at 02:04:05PM -0600, Mario Limonciello wrote:
> > > Hi,
> > >
> > > There was a commit in 6.18 that caused a problem:
> > > c918e75e1ed9 ("drm/amd/display: Add an HPD filter for HDMI")
> > >
> > > This has been fixed by these commits:
> > > commit 6a681cd90345 ("drm/amd/display: Add an hdmi_hpd_debounce_delay_ms
> > > module")
> > > commit 17b2c526fd80 ("drm/amd/display: Clear HDMI HPD pending work only if
> > > it is enabled")
> > >
> > > Can we please bring to 6.18.y and 6.19.y?
> >
> > These only apply to 6.18.y, but not 6.19.y, so can you provide a working
> > backport for both?
> >
>
> It looks like 6.19.y already picked them up!
I thought so, but for some reason my tools couldn't find that. Ah, it
was one of those "cherry picked from" drm nonsense patches. Ugh, what a
mess, I don't know why my tools didn't notice this, normally it does for
the intel patches that show up in the tree like this.
Maybe something is busted on my end with the 6.19->7.0-rc1 transition
that my tools couldn't handle. I thought I found all the corner cases
of that, but as it only happens every few years, odds are I missed
something somewhere...
Anyway, I'll go queue these two up for just 6.18, thanks.
greg k-h
prev parent reply other threads:[~2026-02-25 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 20:04 A few HDMI fixes for 6.18.y Mario Limonciello
2026-02-25 0:56 ` Greg KH
2026-02-25 2:31 ` Mario Limonciello
2026-02-25 14:23 ` 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=2026022524-carbon-paltry-1db0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Renjith.Pananchikkal@amd.com \
--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