mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: "Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Sireesh Kodali" <sireeshkodali@protonmail.com>,
	"Adam Skladowski" <a_skl39@protonmail.com>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Vladimir Lypak" <junak.pub@gmail.com>,
	"Otto Pflüger" <otto.pflueger@abscue.de>,
	"Barnabás Czémán" <barnabas.czeman@mainlining.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MSM8917/MSM8953 Remove ALWAYS_ON flag from cpp_gdsc
Date: Wed,  7 Jan 2026 12:38:16 -0600	[thread overview]
Message-ID: <176781109961.3262943.7043862169715494791.b4-ty@kernel.org> (raw)
In-Reply-To: <20251117-fix-gdsc-cpp-msm8917-msm8953-v1-0-db33adcff28a@mainlining.org>


On Mon, 17 Nov 2025 18:58:46 +0100, Barnabás Czémán wrote:
> cpp_gdsc should not be always on, ALWAYS_ON flag was set accidentally.
> The flags were used for debugging purpose and they were left as always on
> at the gcc drivers submissions.
> 
> 

Applied, thanks!

[1/2] clk: qcom: gcc-msm8953: Remove ALWAYS_ON flag from cpp_gdsc
      commit: 5f613e7034187179a9d088ff5fd02b1089d0cf20
[2/2] clk: qcom: gcc-msm8917: Remove ALWAYS_ON flag from cpp_gdsc
      commit: e4eb42f290aecac0ba355b1f8d7243be6de11f32

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2026-01-07 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 17:58 Barnabás Czémán
2025-11-17 17:58 ` [PATCH 1/2] clk: qcom: gcc-msm8953: " Barnabás Czémán
2025-11-18  9:33   ` Konrad Dybcio
2025-11-17 17:58 ` [PATCH 2/2] clk: qcom: gcc-msm8917: " Barnabás Czémán
2025-11-18  9:33   ` Konrad Dybcio
2026-01-07 18:38 ` 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=176781109961.3262943.7043862169715494791.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=a_skl39@protonmail.com \
    --cc=barnabas.czeman@mainlining.org \
    --cc=junak.pub@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=otto.pflueger@abscue.de \
    --cc=sboyd@kernel.org \
    --cc=sireeshkodali@protonmail.com \
    /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

all inboxes | Powered by JetHome®