From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: nvidia,tegra20-pmc: Move fixed string property names under 'properties'
Date: Thu, 7 Jul 2022 09:22:31 +0200 [thread overview]
Message-ID: <YsaJtzvG7V1bfjGB@orome> (raw)
In-Reply-To: <20220706212034.568861-1-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Wed, Jul 06, 2022 at 03:20:34PM -0600, Rob Herring wrote:
> Fixed string property names should be under 'properties' rather than
> 'patternProperties'. Additionally, without beginning and end of line
> anchors, any prefix or suffix is allowed on the specified property names.
>
> As all the nvidia,tegra20-pmc powergates child node properties are fixed
> strings, change 'patternProperties' to 'properties'.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This is part of a local patch that I have that cleans up other aspects
of this schema as well.
However, I don't know when I'll get around to send that out, so if you
want to apply this in the meantime:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-07 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 21:20 [PATCH] dt-bindings: arm: nvidia,tegra20-pmc: Move fixed string property names under 'properties' Rob Herring
2022-07-07 7:22 ` Thierry Reding [this message]
2022-07-11 19:06 ` Rob Herring
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=YsaJtzvG7V1bfjGB@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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 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).