mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Maulik Shah <maulik.shah@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Marijn Suijten <marijn.suijten@somainline.org>,
	Doug Anderson <dianders@chromium.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v5 0/3] soc: qcom: qcom_stats: Add DDR stats
Date: Tue, 17 Jun 2025 16:31:29 -0500	[thread overview]
Message-ID: <175019588861.714929.10584008229873592706.b4-ty@kernel.org> (raw)
In-Reply-To: <20250611-ddr_stats_-v5-0-24b16dd67c9c@oss.qualcomm.com>


On Wed, 11 Jun 2025 11:33:44 +0530, Maulik Shah wrote:
> This series adds support to read various DDR low power mode and frequency
> stats. This was added in past with series [1] but reverted with [4] due
> to some SoCs boot up failures. This series is more aligned to downstream
> implementation and fixes the issues mentioned in [4].
> 
> The series [1] tried to add three feature support
> 
> [...]

Applied, thanks!

[3/3] arm64: dts: qcom: Add QMP handle for qcom_stats
      commit: 49b1c8df672a2a6229798e4f4088ce90ed44a103

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

      parent reply	other threads:[~2025-06-17 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  6:03 Maulik Shah
2025-06-11  6:03 ` [PATCH v5 1/3] soc: qcom: qcom_stats: Add support to read DDR statistic Maulik Shah
2025-06-11  6:03 ` [PATCH v5 2/3] soc: qcom: qcom_stats: Add QMP support for syncing ddr stats Maulik Shah
2025-06-16  0:20   ` Dmitry Baryshkov
2025-06-11  6:03 ` [PATCH v5 3/3] arm64: dts: qcom: Add QMP handle for qcom_stats Maulik Shah
2025-06-17 21:31 ` 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=175019588861.714929.10584008229873592706.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@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=marijn.suijten@somainline.org \
    --cc=maulik.shah@oss.qualcomm.com \
    --cc=robh@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

all inboxes | Powered by JetHome®