public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: Regression in 6.1.35 / 6.3.9
Date: Tue, 11 Jul 2023 22:12:03 +0200	[thread overview]
Message-ID: <2023071157-shower-dropout-242d@gregkh> (raw)
In-Reply-To: <bcbd0e64-dd21-7d0e-7bcc-b700fe0674e3@amd.com>

On Fri, Jul 07, 2023 at 11:45:57AM -0500, Limonciello, Mario wrote:
> On 7/3/2023 14:06, Salvatore Bonaccorso wrote:
> > Hi Mario,
> > 
> > On Mon, Jul 03, 2023 at 12:43:06PM -0500, Mario Limonciello wrote:
> > > On 7/3/23 08:57, Salvatore Bonaccorso wrote:
> > > > Hi Mario,
> > > > 
> > > > On Wed, Jun 28, 2023 at 08:16:25PM +0200, Greg KH wrote:
> > > > > On Wed, Jun 28, 2023 at 05:56:01PM +0000, Limonciello, Mario wrote:
> > > > > > [Public]
> > > > > > 
> > > > > > Hi,
> > > > > >    A regression was reported in 6.4-rc6 that monitor resolutions are no longer present for anything but native resolution on eDP panels.  This specific change backported into stable at 6.1.35 and 6.3.9:
> > > > > > e749dd10e5f29 ("drm/amd/display: edp do not add non-edid timings")
> > > > > > 
> > > > > > After discussing it with the original author, they submitted a revert commit for review:
> > > > > > https://patchwork.freedesktop.org/patch/544273/
> > > > > > 
> > > > > > I suggested the revert also CC stable, and I expect this will go up in 6.5-rc1, but given the timing of the merge window and the original issue hit the stable trees, can we revert it sooner in the stable
> > > > > > trees to avoid exposing the regression to more people?
> > > > > 
> > > > > As the submitted patch had the wrong git id, it might be good to be able
> > > > > to take a real one?  I can take it once it shows up in linux-next if
> > > > > it's really going to be going into 6.5, but I need a stable git id for
> > > > > it.
> > > > 
> > > > Do you know, did that felt trough the cracks or is it still planned to
> > > > do the revert?
> > > > 
> > > > Regards,
> > > > Salvatore
> > > 
> > > Hi,
> > > 
> > > It's part of the PR that was sent for 6.5-rc1 [1]. Unfortunately it's not
> > > yet merged AFAICT to drm-next yet nor Linus' tree.
> > > 
> > > d6149086b45e [2] is the specific commit ID.
> > > 
> > > [1] https://patchwork.freedesktop.org/patch/545125/
> > > [2] https://gitlab.freedesktop.org/agd5f/linux/-/commit/d6149086b45e150c170beaa4546495fd1880724c
> > 
> > Ack, thanks!
> > 
> > Regards,
> > Salvatore
> 
> The revert is in Linus' tree as of this morning.  Greg, can you take this
> back now?
> 
> d6149086b45e1 ("Revert "drm/amd/display: edp do not add non-edid timings"")

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-07-11 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 17:56 Regression in 6.1.35 / 6.3.9 Limonciello, Mario
2023-06-28 18:16 ` Greg KH
2023-07-03 13:57   ` Salvatore Bonaccorso
2023-07-03 17:43     ` Mario Limonciello
2023-07-03 19:06       ` Salvatore Bonaccorso
2023-07-07 16:45         ` Limonciello, Mario
2023-07-11 20:12           ` 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=2023071157-shower-dropout-242d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.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