From: Rob Herring <robh@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Hector Yuan <hector.yuan@mediatek.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains
Date: Thu, 20 May 2021 14:43:34 -0500 [thread overview]
Message-ID: <CAL_JsqK-LpDQWh9RsLsGPEQ53n6s0+Q7ioVikSm1jZuoCWAgnA@mail.gmail.com> (raw)
In-Reply-To: <20210519112041.olwl35irvcbjxrka@bogus>
On Wed, May 19, 2021 at 6:20 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> Hi Rob,
>
> On Mon, May 17, 2021 at 03:45:11PM -0500, Rob Herring wrote:
>
> [...]
>
> > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml:0:0: /example-0/performance-controller@12340000: failed to match any schema with compatible: ['qcom,cpufreq-hw']
> >
> > See https://patchwork.ozlabs.org/patch/1479615
>
> IIUC, such errors due to the fact that the compatible used in the example
> is not in any yaml schema(as it is still in the old txt format). I also
> assume such errors are allowed until the transition is complete and I
> need not fix anything as part of this patch ?
Not allowed because I can't turn this check on by default until we get
rid of the existing 80 or so. But it is a new check and Viresh already
applied, so oh well.
BTW, one of the 80 is 'operating-points-v2' compatible. Hint, hint.
Rob
next prev parent reply other threads:[~2021-05-20 19:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:54 [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains Sudeep Holla
2021-05-17 19:17 ` Rob Herring
2021-05-19 11:23 ` Sudeep Holla
2021-05-20 3:54 ` Viresh Kumar
2021-05-17 20:45 ` Rob Herring
2021-05-19 11:20 ` Sudeep Holla
2021-05-20 19:43 ` Rob Herring [this message]
2021-05-21 4:08 ` Viresh Kumar
2021-05-21 15:24 ` Sudeep Holla
2021-05-24 9:17 ` Viresh Kumar
2021-05-24 10:05 ` Sudeep Holla
2021-10-14 10:56 ` Ulf Hansson
2021-10-14 14:55 ` Sudeep Holla
2021-10-15 9:17 ` Ulf Hansson
2021-10-19 7:24 ` Viresh Kumar
2021-10-19 13:58 ` Ulf Hansson
2021-10-20 6:24 ` Viresh Kumar
2021-10-20 10:25 ` Sudeep Holla
2021-10-21 13:34 ` Ulf Hansson
2021-10-21 15:35 ` Sudeep Holla
2021-10-20 12:11 ` Rob Herring
2021-10-21 13:13 ` Ulf Hansson
2021-10-21 13:33 ` Sudeep Holla
2021-10-21 16:01 ` Ulf Hansson
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=CAL_JsqK-LpDQWh9RsLsGPEQ53n6s0+Q7ioVikSm1jZuoCWAgnA@mail.gmail.com \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.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).