[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YeoUDdDCIFtRik2K@robh.at.kernel.org>
Date: Thu, 20 Jan 2022 20:01:49 -0600
From: Rob Herring <robh@...nel.org>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: devicetree@...r.kernel.org, Taniya Das <tdas@...eaurora.org>,
linux-kernel@...r.kernel.org,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
linux-arm-msm@...r.kernel.org, Andy Gross <agross@...nel.org>,
linux-clk@...r.kernel.org, Philipp Zabel <p.zabel@...gutronix.de>
Subject: Re: [PATCH v2 02/15] dt-bindings: clock: simplify qcom,gcc-apq8064
Documentation
On Fri, Jan 21, 2022 at 02:41:59AM +0100, Ansuel Smith wrote:
> On Thu, Jan 20, 2022 at 07:37:38PM -0600, Rob Herring wrote:
> > On Fri, 21 Jan 2022 00:20:15 +0100, Ansuel Smith wrote:
> > > Simplify qcon,gcc-apq8064 Documentation by using qcom,gcc.yaml as a
> > > template.
> > >
> > > Signed-off-by: Ansuel Smith <ansuelsmth@...il.com>
> > > ---
> > > .../bindings/clock/qcom,gcc-apq8064.yaml | 27 +++----------------
> > > 1 file changed, 3 insertions(+), 24 deletions(-)
> > >
> >
> > 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/clock/qcom,gcc-apq8064.example.dt.yaml:0:0: /example-0/clock-controller@...000: failed to match any schema with compatible: ['qcom,gcc-apq8064']
> >
> > doc reference errors (make refcheckdocs):
> >
> > See https://patchwork.ozlabs.org/patch/1582347
> >
> > This check can fail if there are any dependencies. The base for a patch
> > series is generally the most recent rc1.
> >
> > If you already ran 'make dt_binding_check' and didn't see the above
> > error(s), then make sure 'yamllint' is installed and dt-schema is up to
> > date:
> >
> > pip3 install dtschema --upgrade
> >
> > Please check and re-submit.
> >
>
> Mhh, think these error comes from running the bot with the single change.
> Or the bot runs the test with the previous commits merged?
It should apply the whole series one by one. However, if patch 1 didn't
apply it will still try the rest. It's only smart enough to apply to the
last rc1. Given it's the merge window, I suspect you have dependency in the
next rc1.
Rob
Powered by blists - more mailing lists