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>
Subject: Re: Regression in 6.1.35 / 6.3.9
Date: Wed, 28 Jun 2023 20:16:25 +0200	[thread overview]
Message-ID: <2023062808-mangy-vineyard-4f66@gregkh> (raw)
In-Reply-To: <MN0PR12MB6101C52C4B7FB00702A996EBE224A@MN0PR12MB6101.namprd12.prod.outlook.com>

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.

thanks,

greg k-h

  reply	other threads:[~2023-06-28 18:16 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 [this message]
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

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=2023062808-mangy-vineyard-4f66@gregkh \
    --to=gregkh@linuxfoundation.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