From: Johan Hovold <johan@kernel.org>
To: Leonard Lausen <leonard@lausen.nl>
Cc: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"György Kurucz" <me@kuruczgy.com>,
"Rob Clark" <robdclark@gmail.com>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Sean Paul" <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Jeykumar Sankaran" <jsanka@codeaurora.org>,
stable@vger.kernel.org, "Abel Vesa" <abel.vesa@linaro.org>
Subject: Re: [v2,1/2] drm/msm/dpu1: don't choke on disabling the writeback connector
Date: Wed, 20 Nov 2024 09:32:04 +0100 [thread overview]
Message-ID: <Zz2ehK4KoUbpdbBv@hovoldconsulting.com> (raw)
In-Reply-To: <4f145884-2c91-4e32-a7bc-b439746c6adb@lausen.nl>
On Tue, Nov 19, 2024 at 10:02:33PM -0500, Leonard Lausen wrote:
> The finding is that while 6.10.14 with this patch applied still suffers from
> that regression, 6.11.9 and 6.12 do not face the CRTC state regression.
> Therefore, whatever issue the patch uncovered in older kernels and which
> justified not merging it before due to regressing basic CTM functionality, is
> now fixed. The patch should be good to merge and backport to 6.11, but from my
> perspective should not be backported to older kernels unless the interaction
> with the DRM CRTC state issue is understood and an associated fix backported as
> well.
Thanks for testing. The 6.9 and 6.10 stable trees are EOL and backporting
to 6.11 should not cause any trouble then.
Johan
next prev parent reply other threads:[~2024-11-20 8:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 19:47 [PATCH v2 0/2] drm/msm/dpu: two fixes targeting 6.11 Dmitry Baryshkov
2024-08-02 19:47 ` [PATCH v2 1/2] drm/msm/dpu1: don't choke on disabling the writeback connector Dmitry Baryshkov
2024-08-05 2:27 ` Leonard Lausen
2024-08-07 10:44 ` Dmitry Baryshkov
2024-08-07 15:41 ` Leonard Lausen
2024-08-05 19:19 ` Abhinav Kumar
2024-08-07 10:46 ` Dmitry Baryshkov
2024-08-30 17:36 ` [v2,1/2] " György Kurucz
2024-08-31 14:53 ` Leonard Lausen
2024-08-31 15:47 ` Leonard Lausen
2024-08-31 18:46 ` György Kurucz
2024-08-31 19:00 ` Leonard Lausen
2024-08-31 21:50 ` György Kurucz
2024-11-19 13:52 ` Johan Hovold
2024-11-19 14:33 ` Leonard Lausen
2024-11-19 15:11 ` Johan Hovold
2024-11-20 3:02 ` Leonard Lausen
2024-11-20 8:32 ` Johan Hovold [this message]
2024-11-20 8:39 ` [PATCH v2 1/2] " Johan Hovold
2024-12-06 10:40 ` Johan Hovold
2024-08-02 19:47 ` [PATCH v2 2/2] drm/msm/dpu: don't play tricks with debug macros Dmitry Baryshkov
2024-08-05 19:25 ` Abhinav Kumar
2024-08-27 9:39 ` Konrad Dybcio
2024-08-28 19:38 ` Dmitry Baryshkov
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=Zz2ehK4KoUbpdbBv@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jsanka@codeaurora.org \
--cc=leonard@lausen.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=me@kuruczgy.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.