All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please pick up 3a9626c816db90 ("drm/amd: Stop evicting resources on APUs in suspend") for linux-6.7.y
Date: Fri, 23 Feb 2024 16:35:00 +0100	[thread overview]
Message-ID: <2024022353-drinking-gala-7ca2@gregkh> (raw)
In-Reply-To: <b743d91f-5e7d-4701-b515-5c2a84ebd291@leemhuis.info>

On Thu, Feb 22, 2024 at 10:04:15AM +0100, Thorsten Leemhuis wrote:
> Hi Greg! Could you please pick up 3a9626c816db90 ("drm/amd: Stop
> evicting resources on APUs in suspend") for the earliest convenient
> linux-6.7.y release? It together with another commit (91636168531909
> ("Revert "drm/amd: flush any delayed gfxoff on suspend entry"")) that is
> also queued for 6.7.6 fixes suspend problems that apparently bother
> quite a few people:
> https://gitlab.freedesktop.org/drm/amd/-/issues/3132
> 
> Both come from the same series (note, patch 3 of that series was deferred):
> https://lore.kernel.org/all/20240208055256.130917-1-mario.limonciello@amd.com/
> 
> Mario, who authored 3a9626c816db90, forgot to add a stable tag and ask
> me to send this mail:
> https://gitlab.freedesktop.org/drm/amd/-/issues/3132#note_2292543

Now queued up, thanks.

greg k-h

      reply	other threads:[~2024-02-23 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  9:04 Please pick up 3a9626c816db90 ("drm/amd: Stop evicting resources on APUs in suspend") for linux-6.7.y Thorsten Leemhuis
2024-02-23 15:35 ` 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=2024022353-drinking-gala-7ca2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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 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.