Linux kernel -stable discussions
 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>,
	"Linux kernel regressions list" <regressions@lists.linux.dev>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Jani Nikula" <jani.nikula@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Kurt Garloff" <kurt@garloff.de>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Sasha Levin" <sashal@kernel.org>
Subject: Re: Drop 0fc6fea41c71 ("drm/i915: Disable DC states for all commits") from the 6.0.y series?
Date: Wed, 9 Aug 2023 11:15:53 +0200	[thread overview]
Message-ID: <2023080930-overturn-duo-17de@gregkh> (raw)
In-Reply-To: <f0870e8f-0c66-57fd-f95d-18d014a11939@leemhuis.info>

On Mon, Aug 07, 2023 at 12:52:03PM +0200, Thorsten Leemhuis wrote:
> Hi Greg! Months ago you picked up mainline commit a2b6e99d8a6
> ("drm/i915: Disable DC states for all commits") for the 6.1.23 release
> as commit 0fc6fea41c71. It causes issues vor a few people (at least
> three, two of which are CCed) -- apparently because it depends on some
> change that wasn't picked up for 6.1.y. This is known for a while now,
> but nobody has yet found which change that is (Al found something that
> worked for him, but that didn't work for others). For the whole story
> skim this ticket:
> 
> https://gitlab.freedesktop.org/drm/intel/-/issues/8419
> 
> I wonder if it might be better if you revert that commit for 6.0.y; I
> asked already in the ticket if this is likely to cause regressions for
> users of 6.0.y, but got no answer from the i915 devs (or did I miss
> something?). :-/

Now reverted (note, 6.0.y is long dead, I reverted this for 6.1.y)

thanks,

greg "drowning in kernel release numbers" k-h

  reply	other threads:[~2023-08-09  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 10:52 Drop 0fc6fea41c71 ("drm/i915: Disable DC states for all commits") from the 6.0.y series? Thorsten Leemhuis
2023-08-09  9:15 ` Greg KH [this message]
2023-08-10 11:31   ` Thorsten Leemhuis
2023-08-11  7:15     ` 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=2023080930-overturn-duo-17de@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jani.nikula@intel.com \
    --cc=kurt@garloff.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    --cc=viro@zeniv.linux.org.uk \
    /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