public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: stable@vger.kernel.org, sashal@kernel.org,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] Revert "drm/amd/pm: correct the workload setting"
Date: Sat, 16 Nov 2024 15:51:20 +0100	[thread overview]
Message-ID: <2024111653-storm-haste-2272@gregkh> (raw)
In-Reply-To: <CADnq5_PkG8JywBPj5mivspUPJUC6chEGuNEH5a1_A-FCd_8wog@mail.gmail.com>

On Sat, Nov 16, 2024 at 08:48:58AM -0500, Alex Deucher wrote:
> On Sat, Nov 16, 2024 at 8:47 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sat, Nov 16, 2024 at 08:04:27AM -0500, Alex Deucher wrote:
> > > This reverts commit 4a18810d0b6fb2b853b75d21117040a783f2ab66.
> > >
> > > This causes a regression in the workload selection.
> > > A more extensive fix is being worked on for mainline.
> > > For stable, revert.
> >
> > Why is this not reverted in Linus's tree too?  Why is this only for a
> > stable tree?  Why can't we take what will be in 6.12?
> 
> I'm about to send out the patch for 6.12 as well, but I want to make
> sure it gets into 6.11 before it's EOL.

If 6.11 is EOL, there's no need to worry about it :)

I'd much prefer to take the real patch please.

thanks,

greg k-h

  reply	other threads:[~2024-11-16 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 13:04 [PATCH] Revert "drm/amd/pm: correct the workload setting" Alex Deucher
2024-11-16 13:46 ` Greg KH
2024-11-16 13:48   ` Alex Deucher
2024-11-16 14:51     ` Greg KH [this message]
2024-11-16 15:07       ` Alex Deucher
2024-11-16 16:06         ` Greg KH
2024-11-18 14:09           ` Alex Deucher
2024-11-18 14:22             ` 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=2024111653-storm-haste-2272@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=sashal@kernel.org \
    --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