From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Manaf Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>,
Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rajendra Nayak <rajendra.nayak@oss.qualcomm.com>,
Pragnesh Papaniya <pragnesh.papaniya@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Misc BWMON fixes for glymur/mahua
Date: Wed, 25 Mar 2026 22:19:26 -0500 [thread overview]
Message-ID: <177449516596.60308.17541233624252365720.b4-ty@kernel.org> (raw)
In-Reply-To: <20260325-bwmon_fixes-v1-0-9433f9d4c276@oss.qualcomm.com>
On Wed, 25 Mar 2026 21:51:49 +0530, Pragnesh Papaniya wrote:
> This series adds the missing opp entry for Glymur/Mahua SoCs and deletes
> bwmon node that corresponds to non-existent cluster2 for Mahua SoCs.
>
>
Applied, thanks!
[1/2] arm64: dts: qcom: glymur: Add missing opp entry
commit: 6921e10a808ab261974b5800e175b6e284b4ff6f
[2/2] arm64: dts: qcom: mahua: Fix mahua bwmon
commit: 8e1f585aab4f044d49cf5147d89a6edaa90273c8
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-26 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 16:21 [PATCH 0/2] Misc BWMON fixes for glymur/mahua Pragnesh Papaniya
2026-03-25 16:21 ` [PATCH 1/2] arm64: dts: qcom: glymur: Add missing opp entry Pragnesh Papaniya
2026-03-25 16:21 ` [PATCH 2/2] arm64: dts: qcom: mahua: Fix mahua bwmon Pragnesh Papaniya
2026-03-25 17:16 ` Dmitry Baryshkov
2026-03-26 3:19 ` 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=177449516596.60308.17541233624252365720.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gopikrishna.garmidi@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=pragnesh.papaniya@oss.qualcomm.com \
--cc=rajendra.nayak@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.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