From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "ekigwana@gmail.com" <ekigwana@gmail.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH 2/3] dt-bindings: iio: frequency: Add docs for ADF4360 PLL
Date: Wed, 22 Jan 2020 07:58:17 +0000 [thread overview]
Message-ID: <f5a39017a50141574c1ab87724bb406043190fe4.camel@analog.com> (raw)
In-Reply-To: <20200121180614.GA9314@bogus>
On Tue, 2020-01-21 at 12:06 -0600, Rob Herring wrote:
> On Tue, 21 Jan 2020 13:25:55 +0200, Alexandru Ardelean wrote:
> > From: Edward Kigwana <ekigwana@gmail.com>
> >
> > This change adds the device-tree bindings documentation for the ADF4360
> > family of PLLs.
> >
> > Signed-off-by: Edward Kigwana <ekigwana@gmail.com>
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > .../bindings/iio/frequency/adi,adf4360.yaml | 158 ++++++++++++++++++
> > 1 file changed, 158 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/iio/frequency/adi,adf4360.yaml
> >
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
urgs...
apologies for forgetting to run this;
and many thanks to your bot;
will fix;
i think i have too much distribution for my attention, and i forget stuff;
well, i'll still have to see about more improvements for our ci
> warning: no schema found in file:
> Documentation/devicetree/bindings/iio/frequency/adi,adf4360.yaml
> /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/iio/frequency/adi,adf4360.yaml:
> ignoring, error parsing file
> Documentation/devicetree/bindings/iio/frequency/adi,adf4360.yaml: while
> scanning a simple key
> in "<unicode string>", line 98, column 5
> could not find expected ':'
> in "<unicode string>", line 99, column 5
> Documentation/devicetree/bindings/Makefile:12: recipe for target
> 'Documentation/devicetree/bindings/iio/frequency/adi,adf4360.example.dts'
> failed
> make[1]: ***
> [Documentation/devicetree/bindings/iio/frequency/adi,adf4360.example.dts]
> Error 1
> Makefile:1263: recipe for target 'dt_binding_check' failed
> make: *** [dt_binding_check] Error 2
>
> See https://patchwork.ozlabs.org/patch/1226401
> Please check and re-submit.
next prev parent reply other threads:[~2020-01-22 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 11:25 [PATCH 1/3] iio: frequency: adf4360: Add support for ADF4360 PLLs Alexandru Ardelean
2020-01-21 11:25 ` [PATCH 2/3] dt-bindings: iio: frequency: Add docs for ADF4360 PLL Alexandru Ardelean
2020-01-21 18:06 ` Rob Herring
2020-01-22 7:58 ` Ardelean, Alexandru [this message]
2020-01-21 11:25 ` [PATCH 3/3] MAINTAINERS: add entry for ADF4360 PLL driver Alexandru Ardelean
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=f5a39017a50141574c1ab87724bb406043190fe4.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=ekigwana@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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).