From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
devicetree@vger.kernel.org, "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald" <pmeerw@pmeerw.net>,
"Mark Rutland" <mark.rutland@arm.com>
Subject: Re: [PATCH v4 2/2] dt-bindings: iio: Add ltc2983 documentation
Date: Tue, 15 Oct 2019 21:44:35 +0100 [thread overview]
Message-ID: <20191015214435.5d51835a@archlinux> (raw)
In-Reply-To: <CAL_Jsq+Hju1KtvfjEJNGsS9maC3LDn0FcQJe6Wp+y-YgiAP=+w@mail.gmail.com>
On Tue, 15 Oct 2019 09:19:10 -0500
Rob Herring <robh@kernel.org> wrote:
> On Mon, Oct 14, 2019 at 9:39 AM Rob Herring <robh@kernel.org> wrote:
> >
> > On Sat, Oct 12, 2019 at 11:57:45AM +0100, Jonathan Cameron wrote:
> > > On Fri, 11 Oct 2019 10:40:38 +0200
> > > Nuno Sá <nuno.sa@analog.com> wrote:
> > >
> > > > Document the LTC2983 temperature sensor devicetree bindings.
> > > >
> > > > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > >
> > > I'm happy with this, but will be waiting for Rob to have a chance
> > > for a final look before applying.
> >
> > LGTM, but I need to add the int64-matrix type to the core schema first
> > or this will give you errors. I should get to that in the next day or
> > so.
>
> Now added, so please update dtschema and check.
>
> Reviewed-by: Rob Herring <robh@kernel.org>
/home/jic23/src/kernel/iio/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.example.dt.yaml: ltc2983@0: thermocouple@20:adi,custom-thermocouple:0:0: 18446744073659331616 is greater than the maximum of 9223372036854775807
/home/jic23/src/kernel/iio/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.example.dt.yaml: ltc2983@0: thermocouple@20:adi,custom-thermocouple:0:2: 18446744073679351616 is greater than the maximum of 9223372036854775807
/home/jic23/src/kernel/iio/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.example.dt.yaml: ltc2983@0: thermocouple@20:adi,custom-thermocouple:0:4: 18446744073704251616 is greater than the maximum of 9223372036854775807
Which is odd. I haven't looked into it beyond testing and reverting the
patch as out of time for today.
Thanks,
Jonathan
next prev parent reply other threads:[~2019-10-15 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 8:40 [PATCH v4 1/2] iio: temperature: Add support for LTC2983 Nuno Sá
2019-10-11 8:40 ` [PATCH v4 2/2] dt-bindings: iio: Add ltc2983 documentation Nuno Sá
2019-10-12 10:57 ` Jonathan Cameron
2019-10-14 14:39 ` Rob Herring
2019-10-15 14:19 ` Rob Herring
2019-10-15 20:44 ` Jonathan Cameron [this message]
2019-10-21 15:27 ` Jonathan Cameron
2019-10-21 17:21 ` Rob Herring
2019-10-22 10:23 ` Jonathan Cameron
2019-10-12 11:04 ` [PATCH v4 1/2] iio: temperature: Add support for LTC2983 Jonathan Cameron
2019-10-22 10:34 ` Jonathan Cameron
2019-10-22 11:57 ` Sa, Nuno
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=20191015214435.5d51835a@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nuno.sa@analog.com \
--cc=pmeerw@pmeerw.net \
--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).