From: Lukasz Luba <lukasz.luba@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, daniel.lezcano@linaro.org,
mka@chromium.org, robh+dt@kernel.org, dianders@chromium.org,
linux-kernel@vger.kernel.org, rnayak@codeaurora.org,
rjw@rjwysocki.net, qperret@google.com, amitk@kernel.org,
corbet@lwn.net, Dietmar.Eggemann@arm.com
Subject: Re: [PATCH v2 3/3] dt-bindings: thermal: update sustainable-power with abstract scale
Date: Mon, 5 Oct 2020 17:14:57 +0100 [thread overview]
Message-ID: <e27273cc-81d7-65fb-b99a-ecebc3efe74c@arm.com> (raw)
In-Reply-To: <20201005135837.GA91584@bogus>
Hi Rob,
On 10/5/20 2:58 PM, Rob Herring wrote:
> On Fri, 02 Oct 2020 12:44:26 +0100, Lukasz Luba wrote:
>> Update the documentation for the binding 'sustainable-power' and allow
>> to provide values in an abstract scale. It is required when the cooling
>> devices use an abstract scale for their power values.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>> .../devicetree/bindings/thermal/thermal-zones.yaml | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> Traceback (most recent call last):
> File "/usr/local/bin/dt-extract-example", line 45, in <module>
> binding = yaml.load(open(args.yamlfile, encoding='utf-8').read())
> File "/usr/local/lib/python3.8/dist-packages/ruamel/yaml/main.py", line 343, in load
> return constructor.get_single_data()
> File "/usr/local/lib/python3.8/dist-packages/ruamel/yaml/constructor.py", line 111, in get_single_data
> node = self.composer.get_single_node()
> File "_ruamel_yaml.pyx", line 706, in _ruamel_yaml.CParser.get_single_node
> File "_ruamel_yaml.pyx", line 724, in _ruamel_yaml.CParser._compose_document
> File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
> File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
> File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
> File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
> File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
> File "_ruamel_yaml.pyx", line 731, in _ruamel_yaml.CParser._compose_node
> File "_ruamel_yaml.pyx", line 904, in _ruamel_yaml.CParser._parse_next_event
> ruamel.yaml.scanner.ScannerError: while scanning a plain scalar
> in "<unicode string>", line 102, column 11
> found a tab character that violates indentation
> in "<unicode string>", line 103, column 1
> make[1]: *** [Documentation/devicetree/bindings/Makefile:18: Documentation/devicetree/bindings/thermal/thermal-zones.example.dts] Error 1
> make[1]: *** Deleting file 'Documentation/devicetree/bindings/thermal/thermal-zones.example.dts'
> make[1]: *** Waiting for unfinished jobs....
> ./Documentation/devicetree/bindings/thermal/thermal-zones.yaml: while scanning a plain scalar
> in "<unicode string>", line 102, column 11
> found a tab character that violates indentation
> in "<unicode string>", line 103, column 1
> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/thermal/thermal-zones.yaml: ignoring, error parsing file
> warning: no schema found in file: ./Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> make: *** [Makefile:1366: dt_binding_check] Error 2
>
>
> See https://patchwork.ozlabs.org/patch/1375670
>
> If you already ran 'make dt_binding_check' and didn't see the above
> error(s), then make sure dt-schema is up to date:
>
> pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
>
> Please check and re-submit.
>
My apologies, I have put tabs instead of spaces in there.
I have run this command and now it passed.
I will resend the patch 3/3.
Regards,
Lukasz
next prev parent reply other threads:[~2020-10-05 16:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 11:44 [PATCH v2 0/3] Clarify abstract scale usage for power values in Energy Model, EAS and IPA Lukasz Luba
2020-10-02 11:44 ` [PATCH v2 1/3] docs: Clarify abstract scale usage for power values in Energy Model Lukasz Luba
2020-10-02 11:44 ` [PATCH v2 2/3] PM / EM: update the comments related to power scale Lukasz Luba
2020-10-02 11:44 ` [PATCH v2 3/3] dt-bindings: thermal: update sustainable-power with abstract scale Lukasz Luba
2020-10-02 14:31 ` Doug Anderson
2020-10-02 15:12 ` Lukasz Luba
2020-10-02 15:47 ` Doug Anderson
2020-10-02 16:40 ` Lukasz Luba
2020-10-02 17:39 ` Doug Anderson
2020-10-06 22:24 ` Rob Herring
2020-10-07 1:17 ` Doug Anderson
2020-10-07 13:26 ` Rob Herring
2020-10-07 21:40 ` Doug Anderson
2020-10-08 14:20 ` Lukasz Luba
2020-10-08 16:41 ` Doug Anderson
2020-10-07 9:03 ` Lukasz Luba
2020-10-05 13:58 ` Rob Herring
2020-10-05 16:14 ` Lukasz Luba [this message]
2020-10-09 9:16 ` [PATCH v2 0/3] Clarify abstract scale usage for power values in Energy Model, EAS and IPA Lukasz Luba
2020-10-14 8:22 ` Daniel Lezcano
2020-10-14 9:08 ` Lukasz Luba
2020-10-14 11:23 ` Daniel Lezcano
2020-10-14 15:24 ` Lukasz Luba
2020-10-14 17:10 ` Daniel Lezcano
2020-10-15 9:00 ` Lukasz Luba
2020-10-15 10:21 ` Daniel Lezcano
2020-10-15 13:40 ` Rafael J. Wysocki
2020-10-15 15:04 ` Quentin Perret
2020-10-16 11:48 ` Daniel Lezcano
2020-10-16 12:18 ` Quentin Perret
2020-10-16 12:50 ` Daniel Lezcano
2020-10-16 13:09 ` Quentin Perret
2020-10-16 14:36 ` Doug Anderson
2020-10-16 15:55 ` Quentin Perret
2020-10-16 14:42 ` Lukasz Luba
2020-10-16 16:02 ` Quentin Perret
2020-10-19 10:35 ` Lukasz Luba
2020-10-15 13:33 ` Rafael J. Wysocki
2020-10-15 13:39 ` Daniel Lezcano
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=e27273cc-81d7-65fb-b99a-ecebc3efe74c@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=amitk@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=qperret@google.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.