From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
David Brown <david.brown@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: rpmhpd: Set 'active_only' for active only power domains
Date: Tue, 19 Nov 2019 17:36:08 -0800 [thread overview]
Message-ID: <20191120013608.GB3143381@builder> (raw)
In-Reply-To: <CAD=FV=WD4r-GAM6mnTg9qB04aaX7JJzHajhtb+N8Yq9UR1WZAA@mail.gmail.com>
On Mon 18 Nov 08:19 PST 2019, Doug Anderson wrote:
> Bjorn / Andy,
>
> On Thu, Feb 14, 2019 at 9:36 AM Douglas Anderson <dianders@chromium.org> wrote:
> >
> > The 'active_only' attribute was accidentally never set to true for any
> > power domains meaning that all the code handling this attribute was
> > dead.
> >
> > NOTE that the RPM power domain code (as opposed to the RPMh one) gets
> > this right.
> >
> > Fixes: 279b7e8a62cc ("soc: qcom: rpmhpd: Add RPMh power domain driver")
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > ---
> >
> > drivers/soc/qcom/rpmhpd.c | 2 ++
> > 1 file changed, 2 insertions(+)
>
> Somehow this fell through the cracks and was never applied. Can you
> pick it up? Given that it's been a year and nobody has noticed this
> it seems like 5.5 is fine, but maybe you could add Cc: stable since it
> seems like something that stable trees would want...
>
> Thanks!
>
Thanks for noticing, I've picked this up.
Regards,
Bjorn
prev parent reply other threads:[~2019-11-20 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 17:36 [PATCH] soc: qcom: rpmhpd: Set 'active_only' for active only power domains Douglas Anderson
2019-02-14 18:23 ` Stephen Boyd
2019-02-15 2:32 ` Rajendra Nayak
2019-11-18 16:19 ` Doug Anderson
2019-11-20 1:36 ` Bjorn Andersson [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=20191120013608.GB3143381@builder \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=swboyd@chromium.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