All of lore.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: Missing 6.0/6.1 stable patch
Date: Wed, 4 Jan 2023 06:36:58 +0100	[thread overview]
Message-ID: <Y7UQetSAU0FM9F37@kroah.com> (raw)
In-Reply-To: <MN0PR12MB6101EB028DE354FAE5C1444DE2F59@MN0PR12MB6101.namprd12.prod.outlook.com>

On Wed, Jan 04, 2023 at 03:43:48AM +0000, Limonciello, Mario wrote:
> [Public]
> 
> Hi,
> 
> This below patch from 6.2-rc1 was Cc to stable 6.0/6.1:
> 
> afa6646b1c5d ("drm/amdgpu: skip MES for S0ix as well since it's part of GFX")
> 
> However It didn't get picked up for 6.0.16 or 6.1.2.  I also didn't see it in stable-queue.git/tree/queue-6.0 or stable-queue.git/tree/queue-6.1.
> 
> I double checked and it works on both 6.0.y and 6.1.y, and It fixes a bad suspend problem, so I wanted to double check it didn't get missed with the holiday shuffle.

It is still in my "to apply" queue.  Due to everyone loving to sneak in
fixes into -rc1 instead of getting them to Linus sooner for -final, the
queue is huge at this point in time with over 200+ remaining for me to
go through.  Add to that the general mess of the DRM tree when it comes
to stable patches for -rc1 (most are duplicates of what is already in
older stable releases), I wait until I have processed _EVERYTHING_ else
before even looking at DRM patches for stable during this time period.

So don't worry, it's not lost, just give us a week or two more to catch
up and please work to try to get fixes into -final whenever possible and
not wait for the huge -rc1 merge for issues that are more urgent.

thanks,

greg k-jh

      reply	other threads:[~2023-01-04  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  3:43 Missing 6.0/6.1 stable patch Limonciello, Mario
2023-01-04  5:36 ` 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=Y7UQetSAU0FM9F37@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.