From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rayyan Ansari <rayyan@ansari.sh>,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Luca Weiss <luca@z3ntu.xyz>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] dt-bindings: iio/adc: qcom,spmi-iadc: document PM8226 compatible
Date: Fri, 30 Dec 2022 17:23:01 +0000 [thread overview]
Message-ID: <20221230172301.6bbfaf3e@jic23-huawei> (raw)
In-Reply-To: <98992679-47bb-24d3-d253-48fefb4a45f5@linaro.org>
On Thu, 29 Dec 2022 09:47:27 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 29/12/2022 00:04, Rayyan Ansari wrote:
> > Document the compatible for the IADC used on PM8226.
> >
> > Signed-off-by: Rayyan Ansari <rayyan@ansari.sh>
>
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Applied to the togreg branch of iio.git and initially pushed out as testing for 0-day
to take a poke at it.
Thanks,
Jonathan
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2022-12-30 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:04 [PATCH v2 0/4] ARM: dts: qcom: pm8226: style fixes and new nodes Rayyan Ansari
2022-12-28 23:04 ` [PATCH v2 1/4] ARM: dts: qcom: pm8226: sort includes alphabetically and nodes by address Rayyan Ansari
2022-12-29 10:14 ` Konrad Dybcio
2022-12-28 23:04 ` [PATCH v2 2/4] ARM: dts: qcom: pm8226: add PON device node along with resin sub-node Rayyan Ansari
2022-12-29 10:36 ` Konrad Dybcio
2022-12-28 23:04 ` [PATCH v2 3/4] ARM: dts: qcom: pm8226: add IADC node Rayyan Ansari
2022-12-29 10:15 ` Konrad Dybcio
2022-12-28 23:04 ` [PATCH v2 4/4] dt-bindings: iio/adc: qcom,spmi-iadc: document PM8226 compatible Rayyan Ansari
2022-12-29 8:47 ` Krzysztof Kozlowski
2022-12-30 17:23 ` Jonathan Cameron [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=20221230172301.6bbfaf3e@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=rayyan@ansari.sh \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).