[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ4Jf0F4jxz2ufH-j3Mxp_B3=CiLfedP+4bneQ=V1AXNQ@mail.gmail.com>
Date: Wed, 26 Jun 2019 13:57:06 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Mircea Caprioru <mircea.caprioru@...log.com>,
Michael Hennerich <Michael.Hennerich@...log.com>,
Stefan Popa <stefan.popa@...log.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@...r.kernel.org>,
devicetree@...r.kernel.org
Subject: Re: [PATCH V4 4/5] dt-bindings: iio: adc: Convert ad7124
documentation to YAML
On Wed, Jun 26, 2019 at 1:34 PM Jonathan Cameron <jic23@...nel.org> wrote:
>
> On Wed, 26 Jun 2019 08:44:36 -0600
> Rob Herring <robh+dt@...nel.org> wrote:
>
> > On Tue, Jun 25, 2019 at 2:12 AM Mircea Caprioru
> > <mircea.caprioru@...log.com> wrote:
> > >
> > > Convert AD7124 bindings documentation to YAML format.
> > >
> > > Signed-off-by: Mircea Caprioru <mircea.caprioru@...log.com>
> > > ---
> > >
> > > Changelog v2:
> > > - modified SPDX license to GPL-2.0 OR BSD-2-Clause
> > > - added regex for a range from 0 to 15
> > > - added minimum and maximum constraints for reg property
> > > - set type and range of values for adi,reference-select property
> > > - used items for diff-channels property
> > > - set bipolar, adi,buffered-positive and negative to type: boolean
> > >
> > > Changelog v3:
> > > - moved adi,buffered-positive and negative properties to own commit
> > >
> > > Changelog v4:
> > > - removed old txt dt-binding
> > >
> > > .../bindings/iio/adc/adi,ad7124.txt | 75 ---------
> > > .../bindings/iio/adc/adi,ad7124.yaml | 144 ++++++++++++++++++
> > > 2 files changed, 144 insertions(+), 75 deletions(-)
> > > delete mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7124.txt
> > > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml
> >
> > Reviewed-by: Rob Herring <robh@...nel.org>
> Something a bit odd happened when trying to apply this, so I ended up doing
> it rather manually.
>
> error: cannot convert from y to UTF-8
> fatal: could not parse patch
>
> Anyhow, I think it's fine now, but would welcome any suggestion on what causes
> that one? Patch was perfectly happy with it.
Looks like an error in the mail header:
Content-Type: text/plain; charset="y"
Rob
Powered by blists - more mailing lists