On Mon, Nov 18, 2024 at 09:09:53AM -0500, Alex Deucher wrote: > On Sat, Nov 16, 2024 at 11:07 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Sat, Nov 16, 2024 at 10:07:38AM -0500, Alex Deucher wrote: > > > On Sat, Nov 16, 2024 at 9:51 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > 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@xxxxxxxxxxxxxxxxxxx> 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 :) > > > > > > End users care :) > > > > > > > > > > > I'd much prefer to take the real patch please. > > > > > > Here's the PR I sent to Dave and Sima: > > > https://lists.freedesktop.org/archives/dri-devel/2024-November/477927.html > > > I didn't cc stable because I had already send this patch to stable in > > > this thread. > > > > I'd much rather prefer to match up with what is in Linus's tree. If you > > have the git id that lands in Linus's tree, please let us know and we > > can take that. This way we can keep 6.11 and 6.12 in sync, right? > > Sure, but if the patch happened to miss 6.12.0, it would have landed > in 6.12.1. If that happened 6.11 may have missed it and right now and > for the near future, 6.11 is what is important to users and distros. > Anyway, the patch landed before 6.12 final, so please pull: > commit 44f392fbf628 ("Revert "drm/amd/pm: correct the workload setting"") > into 6.11 stable. It's already been queued up, happened yesterday :) thanks, greg k-h
