From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Felix Kuehling <felix.kuehling@amd.com>,
amd-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: AMD drm patch workflow is broken for stable trees
Date: Tue, 1 Oct 2024 12:04:06 +0200 [thread overview]
Message-ID: <2024100112-flounder-paralysis-eb25@gregkh> (raw)
In-Reply-To: <CADnq5_MZ8s=jcCt_-=D2huPA=X3f5PWNjMhr88xoiKc_JFwQtw@mail.gmail.com>
On Mon, Sep 30, 2024 at 10:10:25AM -0400, Alex Deucher wrote:
> Resending now that rc1 is out. These should be ignored for stable.
>
> 8151a6c13111 drm/amd/display: Skip Recompute DSC Params if no Stream on Link
> fbfb5f034225 drm/amdgpu: fix contiguous handling for IB parsing v2
> ec0d7abbb0d4 drm/amd/display: Fix Potential Null Dereference
> 332315885d3c drm/amd/display: Remove ASSERT if significance is zero in
> math_ceil2
> 295d91cbc700 drm/amd/display: Check for NULL pointer
> 6472de66c0aa drm/amd/amdgpu: Fix uninitialized variable warnings
> 93381e6b6180 drm/amdgpu: fix a possible null pointer dereference
> 7a38efeee6b5 drm/radeon: fix null pointer dereference in radeon_add_common_modes
Thanks, that helped a lot.
However the following two commits did not apply, is that because they
are already in the tree or do they need someone to properly backport them?
c2ed7002c061 ("drm/amd/display: Use SDR white level to calculate matrix coefficients")
b74571a83fd3 ("drm/amd/display: Use full update for swizzle mode change")
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-01 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:00 AMD drm patch workflow is broken for stable trees Greg KH
2024-08-14 20:39 ` Felix Kuehling
2024-08-14 21:30 ` Alex Deucher
2024-08-15 5:11 ` Greg KH
2024-08-23 21:23 ` Alex Deucher
2024-08-24 5:23 ` Greg KH
2024-08-27 14:18 ` Alex Deucher
2024-09-04 17:23 ` Greg KH
2024-09-30 14:10 ` Alex Deucher
2024-10-01 10:04 ` Greg KH [this message]
2024-10-01 13:19 ` Alex Deucher
2024-08-15 5:12 ` 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=2024100112-flounder-paralysis-eb25@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--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