All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: kgunda@codeaurora.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, linux-arm-msm@vger.kernel.org, pavel@ucw.cz,
	dri-devel@lists.freedesktop.org, daniel.thompson@linaro.org,
	krzysztof.kozlowski+dt@linaro.org, lee.jones@linaro.org,
	linux-kernel@vger.kernel.org, agross@kernel.org,
	bjorn.andersson@linaro.org, krzysztof.kozlowski@linaro.org,
	jingoohan1@gmail.com, linux-leds@vger.kernel.org
Subject: Re: (subset) [PATCH 2/2] arm64: dts: qcom: correct SPMI WLED register range encoding
Date: Wed, 22 Jun 2022 10:35:35 +0200	[thread overview]
Message-ID: <165588692597.15720.6527539957529378086.b4-ty@linaro.org> (raw)
In-Reply-To: <20220505154702.422108-2-krzysztof.kozlowski@linaro.org>

On Thu, 5 May 2022 17:47:02 +0200, Krzysztof Kozlowski wrote:
> On PM660L, PMI8994 and PMI8998, the WLED has two address spaces and with
> size-cells=0, they should be encoded as two separate items.
> 
> 

Applied, thanks!

[2/2] arm64: dts: qcom: correct SPMI WLED register range encoding
      https://git.kernel.org/krzk/linux/c/2559f68b5991be168785a16a53f582862cf0063c

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

  reply	other threads:[~2022-06-22  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 15:47 [PATCH 1/2] dt-bindings: leds: qcom-wled: fix number of addresses Krzysztof Kozlowski
2022-05-05 15:47 ` [PATCH 2/2] arm64: dts: qcom: correct SPMI WLED register range encoding Krzysztof Kozlowski
2022-06-22  8:35   ` Krzysztof Kozlowski [this message]
2022-07-03  3:56   ` (subset) " Bjorn Andersson
2022-05-17  0:11 ` [PATCH 1/2] dt-bindings: leds: qcom-wled: fix number of addresses Rob Herring
2022-05-17  0:11   ` Rob Herring
2022-06-20 19:41 ` (subset) " Krzysztof Kozlowski

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=165588692597.15720.6527539957529378086.b4-ty@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jingoohan1@gmail.com \
    --cc=kgunda@codeaurora.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.