public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH for-5.4.y 0/3] db845c(sdm845) PM runtime fixes
Date: Wed, 21 Feb 2024 11:39:41 +0100	[thread overview]
Message-ID: <2024022130-captivate-gawk-9b93@gregkh> (raw)
In-Reply-To: <CAMi1Hd2jwt4G4f=3Jh5+uoSiVcw_PqKQXcHq1wipF15uwTdbdw@mail.gmail.com>

On Tue, Jan 30, 2024 at 07:22:28PM +0530, Amit Pundir wrote:
> On Mon, 29 Jan 2024 at 22:59, Amit Pundir <amit.pundir@linaro.org> wrote:
> >
> > On Mon, 29 Jan 2024 at 21:51, Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Mon, Jan 29, 2024 at 04:08:59PM +0530, Amit Pundir wrote:
> > > > Hi,
> > > >
> > > > v5.4.y commit 31b169a8bed7 ("drm/msm/dsi: Use pm_runtime_resume_and_get
> > > > to prevent refcnt leaks"), which is commit 3d07a411b4fa upstream, broke
> > > > display on Dragonboard 845c(sdm845). Cherry-picking commit 6ab502bc1cf3
> > > > ("drm/msm/dsi: Enable runtime PM") from the original patch series
> > > > https://patchwork.freedesktop.org/series/119583/
> > > > and it's dependent runtime PM helper routines as suggested by Dmitry
> > > > https://lore.kernel.org/stable/CAA8EJpo7q9qZbgXHWe7SuQFh0EWW0ZxGL5xYX4nckoFGoGAtPw@mail.gmail.com
> > > > fixes that display regression on DB845c.
> > >
> > > We need fixes for all of the newer stable trees too, you can't fix an
> > > issue in an old tree and then if you upgraded, you would run into that
> > > issue again.
> > >
> > > So please, resend this series as a set of series for all active lts
> > > kernels, and we will be glad to queue them up.
> >
> > Ack. I'll send the patch series for all the active LTS kernels
> > tomorrow after build/boot testing them locally. Meanwhile please
> > consider this patch series for v5.4.y anyway.
> 
> Smoke tested and sent relevant fixes for other active LTS kernel
> versions as well.
> 
> v5.10.y https://lore.kernel.org/stable/20240130124630.3867218-1-amit.pundir@linaro.org/T/
> 
> v5.15.y https://lore.kernel.org/stable/20240130125847.3915432-1-amit.pundir@linaro.org/T/
> 
> and v6.1.y+ https://lore.kernel.org/stable/20240130134647.58630-1-amit.pundir@linaro.org/T/

Sorry for the long delay, been busy :(

All now queued up.

greg k-h

      reply	other threads:[~2024-02-21 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 10:38 [PATCH for-5.4.y 0/3] db845c(sdm845) PM runtime fixes Amit Pundir
2024-01-29 10:39 ` [PATCH for-v5.4.y 1/3] PM: runtime: add devm_pm_runtime_enable helper Amit Pundir
2024-01-29 10:39 ` [PATCH for-v5.4.y 2/3] PM: runtime: Have devm_pm_runtime_enable() handle pm_runtime_dont_use_autosuspend() Amit Pundir
2024-01-29 10:39 ` [PATCH for-v5.4.y 3/3] drm/msm/dsi: Enable runtime PM Amit Pundir
2024-01-29 16:21 ` [PATCH for-5.4.y 0/3] db845c(sdm845) PM runtime fixes Greg KH
2024-01-29 17:29   ` Amit Pundir
2024-01-29 17:42     ` Greg KH
2024-01-30 13:52     ` Amit Pundir
2024-02-21 10:39       ` Greg KH [this message]

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=2024022130-captivate-gawk-9b93@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.pundir@linaro.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --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