From: Stephen Boyd <sboyd@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: clock: Convert fixed-clock binding to json-schema
Date: Thu, 24 Jan 2019 14:50:31 -0800 [thread overview]
Message-ID: <154837023198.136743.2813500611695220769@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <CABGGiswYYpm-7T9e6F_Mp6FdU-JFDC8xV_JR1E6cgiz32A0u_Q@mail.gmail.com>
Quoting Rob Herring (2019-01-11 15:09:58)
>
> make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/file/to/test
>
> It will check only the schema specified and check all the DT files
> against only that schema (plus any referenced schema if you use a
> top-level 'allOf'. See the GIC schema patch[2] for an example of
> that).
>
> I'm running the schema check for patches in the DT patchwork instance.
> For example, here's this patch[1]. So as long as it has my R-by, then
> it should be good. I'm not yet running the schema check on DT files
> because generally there are warnings and I don't intend to fix them
> for everyone. But maybe I should anyways so we at least have the data.
>
Ok. I'll apply this patch to clk-next with my small fixes rolled in.
prev parent reply other threads:[~2019-01-24 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 22:19 [PATCH] dt-bindings: clock: Convert fixed-clock binding to json-schema Rob Herring
2019-01-11 17:44 ` Stephen Boyd
2019-01-11 18:27 ` Rob Herring
2019-01-11 18:54 ` Stephen Boyd
2019-01-11 20:49 ` Rob Herring
2019-01-11 22:42 ` Stephen Boyd
2019-01-11 23:09 ` Rob Herring
2019-01-24 22:50 ` Stephen Boyd [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=154837023198.136743.2813500611695220769@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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).