From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree@vger.kernel.org, Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] dt-bindings: gnss: Rewrite sirfstar binding in YAML
Date: Fri, 11 Mar 2022 21:41:25 -0600 [thread overview]
Message-ID: <1647056485.116768.724636.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220311235119.523374-3-linus.walleij@linaro.org>
On Sat, 12 Mar 2022 00:51:18 +0100, Linus Walleij wrote:
> This rewrites the SiRFstar DT bindings in YAML.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> .../devicetree/bindings/gnss/sirfstar.txt | 46 ------------
> .../devicetree/bindings/gnss/sirfstar.yaml | 73 +++++++++++++++++++
> 2 files changed, 73 insertions(+), 46 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/gnss/sirfstar.txt
> create mode 100644 Documentation/devicetree/bindings/gnss/sirfstar.yaml
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/1604572
gnss: 'lna-supply' does not match any of the regexes: 'pinctrl-[0-9]+'
arch/arm/boot/dts/omap3-gta04a3.dt.yaml
arch/arm/boot/dts/omap3-gta04a4.dt.yaml
arch/arm/boot/dts/omap3-gta04a5.dt.yaml
arch/arm/boot/dts/omap3-gta04a5one.dt.yaml
next prev parent reply other threads:[~2022-03-12 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 23:51 [PATCH 1/4] dt-bindings: gnss: Rewrite common bindings in YAML Linus Walleij
2022-03-11 23:51 ` [PATCH 2/4] dt-bindings: gnss: Modify u-blox to use common bindings Linus Walleij
2022-03-12 11:41 ` Krzysztof Kozlowski
2022-03-11 23:51 ` [PATCH 3/4] dt-bindings: gnss: Rewrite sirfstar binding in YAML Linus Walleij
2022-03-12 3:41 ` Rob Herring [this message]
2022-03-11 23:51 ` [PATCH 4/4] dt-bindings: gnss: Add two more chips Linus Walleij
2022-03-12 11:44 ` Krzysztof Kozlowski
2022-03-12 11:39 ` [PATCH 1/4] dt-bindings: gnss: Rewrite common bindings in YAML Krzysztof Kozlowski
2022-03-17 17:54 ` Linus Walleij
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=1647056485.116768.724636.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.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).