From: Jiri Slaby <jirislaby@kernel.org>
To: "Philip Müller" <philm@manjaro.org>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: 'Roman Gilg' <romangg@manjaro.org>
Subject: Re: Regression in 6.11.2
Date: Tue, 8 Oct 2024 06:35:17 +0200 [thread overview]
Message-ID: <d0232dfe-f20b-45b3-b523-e86febe4ad5a@kernel.org> (raw)
In-Reply-To: <602fc890-8924-4ff4-904c-8bc561745b46@manjaro.org>
On 08. 10. 24, 3:35, Philip Müller wrote:
> On 8/10/24 03:33, Mario Limonciello wrote:
>> Hi,
>>
>> commit 872b8f14d772 ("drm/amd/display: Validate backlight caps are
>> sane") was added to stable trees to fix a brightness problem on one
>> laptop on a buggy firmware but with how aggressive it was it caused a
>> problem on another.
>>
>> Fortunately the problem on the other was already fixed in 6.12 though!
>>
>> commit 87d749a6aab7 ("drm/amd/display: Allow backlight to go below
>> `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT`")
>>
>> Can that commit please be brought everywhere that 872b8f14d772 went?
>>
>> Thanks!
>
> So far commit 872b8f14d772 got added to 6.11.2, 6.10.13 and 6.6.54.
> It is also queued up for upcoming 6.1.113 and 5.15.168.
This is confusing -- Mario used a wrong SHA.
The (correct) bad one is:
327e62f47eb5 drm/amd/display: Validate backlight caps are sane
and is present:
queue-5.15/drm-amd-display-validate-backlight-caps-are-sane.patch
queue-6.1/drm-amd-display-validate-backlight-caps-are-sane.patch
releases/6.10.13/drm-amd-display-validate-backlight-caps-are-sane.patch
releases/6.11.2/drm-amd-display-validate-backlight-caps-are-sane.patch
releases/6.6.54/drm-amd-display-validate-backlight-caps-are-sane.patch
The good one is:
87d749a6aab7 drm/amd/display: Allow backlight to go below
`AMDGPU_DM_DEFAULT_MIN_BACKLIGHT`
and is nowhere.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2024-10-08 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 20:33 Regression in 6.11.2 Mario Limonciello
2024-10-08 1:35 ` Philip Müller
2024-10-08 4:35 ` Jiri Slaby [this message]
2024-10-08 6:05 ` Sasha Levin
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=d0232dfe-f20b-45b3-b523-e86febe4ad5a@kernel.org \
--to=jirislaby@kernel.org \
--cc=mario.limonciello@amd.com \
--cc=philm@manjaro.org \
--cc=romangg@manjaro.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;
as well as URLs for NNTP newsgroup(s).