From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Tony Lindgren <tony@atomide.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio/adc: ti,palmas-gpadc: Split interrupt fields in example
Date: Sun, 9 Jan 2022 15:15:53 +0000 [thread overview]
Message-ID: <20220109151553.1c14810d@jic23-huawei> (raw)
In-Reply-To: <20220106182518.1435497-3-robh@kernel.org>
On Thu, 6 Jan 2022 12:25:11 -0600
Rob Herring <robh@kernel.org> wrote:
> Best practice for multi-cell property values is to bracket each multi-cell
> value.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
Applied to the togreg branch of iio.git.
I'm assuming there is no rush on this as it's best practice rather than a bug.
Thanks,
Jonathan
> ---
> .../devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml b/Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml
> index 7b895784e008..57a31356082e 100644
> --- a/Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml
> @@ -74,9 +74,9 @@ examples:
> compatible = "ti,twl6035-pmic", "ti,palmas-pmic";
> adc {
> compatible = "ti,palmas-gpadc";
> - interrupts = <18 0
> - 16 0
> - 17 0>;
> + interrupts = <18 0>,
> + <16 0>,
> + <17 0>;
> #io-channel-cells = <1>;
> ti,channel0-current-microamp = <5>;
> ti,channel3-current-microamp = <10>;
prev parent reply other threads:[~2022-01-09 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 18:25 [PATCH] dt-bindings: iio/adc: ti,palmas-gpadc: Split interrupt fields in example Rob Herring
2022-01-09 15:15 ` 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=20220109151553.1c14810d@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.com \
/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).