From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Sasha Levin <sashal@kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Some 7.1-post fixes that might be worth picking up rather sooner than later
Date: Fri, 19 Jun 2026 11:43:41 +0200 [thread overview]
Message-ID: <2026061917-flinch-idealism-898f@gregkh> (raw)
In-Reply-To: <91281f28-eccf-4681-8f62-faaa8a3ba529@leemhuis.info>
On Fri, Jun 19, 2026 at 08:04:35AM +0200, Thorsten Leemhuis wrote:
> Hi Stable Team! From the regressions point I think it might be nice to
> pick up the following changes for the next round of stable updates (e.g.
> 7.1.2), as they seem to fix regressions I've seen multiple people report
> with 7.1:
>
> * 426e5846eba75f ("HID: Input: Add battery list cleanup with devm action")
> * 12f58a6caad3be ("drm/amd/display: Fix Color Manager (3DLUT, Shaper,
> Blend)") [v7.1-post]
> * 342981fff32802 ("drm/amdgpu: drop retry loop in
> amdgpu_hmm_range_get_pages") [v7.1-post] (Alex provided a backport for
> this in
> https://lore.kernel.org/all/20260616130531.738887-1-alexander.deucher@amd.com/
> - this one affects 7.0.12, too)
I took the first and last for now, the middle one is "big" so I'll wait
for the next round of -rcs for it.
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-19 9:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 6:04 Some 7.1-post fixes that might be worth picking up rather sooner than later Thorsten Leemhuis
2026-06-19 9:43 ` Greg KH [this message]
2026-06-22 5:32 ` Greg KH
2026-07-07 10:19 ` Thorsten Leemhuis
2026-07-07 11:48 ` Greg KH
2026-07-07 14:32 ` Greg KH
2026-07-07 15:19 ` Deucher, Alexander
2026-07-07 15:28 ` Thorsten Leemhuis
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=2026061917-flinch-idealism-898f@gregkh \
--to=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox