On Mon, May 05, 2025 at 10:33:49AM +0200, Janne Grunau wrote:
Hej,
On Mon, May 5, 2025, at 09:53, gregkh@linuxfoundation.org wrote:
The patch below does not apply to the 6.6-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to stable@vger.kernel.org.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y git checkout FETCH_HEAD git cherry-pick -x 32dce6b1949a696dc7abddc04de8cbe35c260217
This works for me without conflicts. Are there git configs which might influence this? The only noticeable thing is that the position of the DRM_DEBUG_DP_MST_TOPOLOGY_REFS entry shifted 82 lines down. I looked at the history of drivers/gpu/drm/Kconfig and the config DRM_DEBUG_DP_MST_TOPOLOGY_REFS block hasn't changed since v5.10. So I would expect the cherry-pick to work.
It applies cleanly, but breaks the build badly. Try it and see :)
Having said all that I don't know how important it is to have this in older stable releases when nobody noticed it before. The issue presents itself only with out-of-tree rust DRM drivers. I don't expect that anyone will try to backport those to old stable releases.
I'm fine with skipping this commit for stable releases for 6.6 and older and won't post backports.
Ok, thanks!
greg k-h