mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 0/3] soc: qcom: llcc: add support for SAR2130P and SAR1130P platforms
Date: Sun,  3 Nov 2024 22:13:41 -0600	[thread overview]
Message-ID: <173069362374.23540.7269942391053238978.b4-ty@kernel.org> (raw)
In-Reply-To: <20241026-sar2130p-llcc-v3-0-2a58fa1b4d12@linaro.org>


On Sat, 26 Oct 2024 18:43:30 +0300, Dmitry Baryshkov wrote:
> Add support for LLCC programming on Qualcomm SAR2130P and SAR1130P
> platforms. These platforms require few additional quirks in order to be
> handled properly.
> 
> 

Applied, thanks!

[1/3] dt-bindings: cache: qcom,llcc: document SAR2130P and SAR1130P
      commit: 53b3e2e0c9a36263be6874203c68bd7bd104663f
[2/3] soc: qcom: llcc: use deciman integers for bit shift values
      commit: 6dd3f08c72d607372db9b96df95fc6f462981ee2
[3/3] soc: qcom: llcc: add support for SAR2130P and SAR1130P
      commit: 1685f685ff8036c74c3b5e9006ec7ceda5bafefa

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

      parent reply	other threads:[~2024-11-04  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 15:43 Dmitry Baryshkov
2024-10-26 15:43 ` [PATCH v3 1/3] dt-bindings: cache: qcom,llcc: document SAR2130P and SAR1130P Dmitry Baryshkov
2024-10-26 15:43 ` [PATCH v3 2/3] soc: qcom: llcc: use deciman integers for bit shift values Dmitry Baryshkov
2024-10-28 15:48   ` Konrad Dybcio
2024-10-26 15:43 ` [PATCH v3 3/3] soc: qcom: llcc: add support for SAR2130P and SAR1130P Dmitry Baryshkov
2024-10-28 15:58   ` Konrad Dybcio
2024-11-04  4:13 ` 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=173069362374.23540.7269942391053238978.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®