From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
linux-iio@vger.kernel.org, robh+dt@kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/9] dt-bindings:iio:samsung,exynos-adc: drop missuse of io-channel-ranges
Date: Tue, 17 Nov 2020 10:49:11 +0100 [thread overview]
Message-ID: <20201117094911.GA13513@kozik-lap> (raw)
In-Reply-To: <20201115192951.1073632-3-jic23@kernel.org>
On Sun, Nov 15, 2020 at 07:29:44PM +0000, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> io-channel-ranges is a property for consumers of io-channels, not
> providers. Hence it is not relevant in this binding or the examples
> given.
>
> Recent changes to dt-schema result int his being reported as an error
s/int his/in this/
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-17 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 19:29 [PATCH 0/9] dt-bindings: IIO: Drop wrong use of io-channel-ranges then drop it as well Jonathan Cameron
2020-11-15 19:29 ` [PATCH 1/9] dt-bindings:iio:qcom-spmi-vadc drop incorrect io-channel-ranges from example Jonathan Cameron
2020-11-28 15:33 ` Jonathan Cameron
2020-11-28 18:26 ` Bjorn Andersson
2020-11-15 19:29 ` [PATCH 2/9] dt-bindings:iio:samsung, exynos-adc: drop missuse of io-channel-ranges Jonathan Cameron
2020-11-17 9:49 ` Krzysztof Kozlowski [this message]
2020-11-28 15:35 ` [PATCH 2/9] dt-bindings:iio:samsung,exynos-adc: " Jonathan Cameron
2020-11-15 19:29 ` [PATCH 3/9] ARM: dts: Cygnus: Drop incorrect io-channel-ranges property Jonathan Cameron
2020-11-16 3:23 ` Florian Fainelli
2020-11-16 9:44 ` Jonathan Cameron
2020-11-15 19:29 ` [PATCH 4/9] ARM: dts: exynos: Drop incorrect use of io-channel-ranges Jonathan Cameron
2020-11-17 19:45 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 5/9] ARM: dts: s5pv210: Drop incorrect use of io-channel-ranges property Jonathan Cameron
2020-11-17 19:46 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 6/9] ARM: dts: qcom-pma8084: Drop incorrect use of io-channel-ranges Jonathan Cameron
2020-11-28 15:37 ` Jonathan Cameron
2020-11-28 18:30 ` Bjorn Andersson
2020-11-28 18:59 ` Jonathan Cameron
2020-11-15 19:29 ` [PATCH 7/9] ARM: dts: s5pv210-aries: Drop unneeded io-channel-ranges property Jonathan Cameron
2020-11-17 19:47 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [PATCH 8/9] arm64: dts: exynos: Drop incorrect use of " Jonathan Cameron
2020-11-17 19:48 ` Krzysztof Kozlowski
2020-11-15 19:29 ` [RFC PATCH 9/9] iio: inkern: Drop io-channel-ranges dt property support Jonathan Cameron
2021-02-21 16:31 ` Jonathan Cameron
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=20201117094911.GA13513@kozik-lap \
--to=krzk@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).