From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, "Siqueira,
Rodrigo" <Rodrigo.Siqueira@amd.com>
Subject: Re: drm/amd/display: Pass pwrseq inst for backlight and ABM
Date: Thu, 5 Dec 2024 15:11:18 +0100 [thread overview]
Message-ID: <2024120502-pedometer-palpitate-62e9@gregkh> (raw)
In-Reply-To: <1733403204@msgid.manchmal.in-ulm.de>
On Thu, Dec 05, 2024 at 02:02:29PM +0100, Christoph Biedl wrote:
> Greg KH wrote...
>
> > On Mon, Dec 02, 2024 at 12:33:48PM +0100, Christoph Biedl wrote:
>
> > > tl;dr: Was it possible to have this in 6.1.y?
> (...)
> > Why not just move to 6.6.y instead? What's preventing that from
> > happening?
>
> Reasons are mostly political, also switching series this is a bigger
> change that naturally requires way more careful testing for regressions.
Then your testing infrastructure is wrong. You need to do careful
testing for every stable release, as we sometimes do "major" things in
them (like rewrite the syscall path, no one noticed that...)
Your testing framework should be the same for any kernel change, "major"
or "minor".
> It will happen somewhen in the next year anyway, a cherry-picked fix
> could have been shipped now-ish. But it seems this is not an option.
Feel free to take it for your own tree if you feel it is needed.
thanks,
greg k-h
prev parent reply other threads:[~2024-12-05 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 16:16 drm/amd/display: Pass pwrseq inst for backlight and ABM Alex Deucher
2024-01-17 16:49 ` Greg KH
2024-01-17 17:21 ` Alex Deucher
2024-01-18 9:57 ` Greg KH
2024-12-02 11:33 ` Christoph Biedl
2024-12-02 12:35 ` Greg KH
2024-12-05 13:02 ` Christoph Biedl
2024-12-05 14:11 ` 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=2024120502-pedometer-palpitate-62e9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel.bfrz@manchmal.in-ulm.de \
--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