From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jerome Neanne <jerome.neanne@baylibre.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
Andrew Davis <afd@ti.com>, Mark Brown <broonie@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH] dt-bindings: Move fixed string node names under 'properties'
Date: Tue, 22 Nov 2022 18:08:31 -0600 [thread overview]
Message-ID: <166916210667.828774.15527231190149112577.robh@kernel.org> (raw)
In-Reply-To: <20221118223708.1721134-1-robh@kernel.org>
On Fri, 18 Nov 2022 16:37:07 -0600, Rob Herring wrote:
> Fixed string node 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 node name.
> These cases don't appear to want a prefix or suffix, so move them under
> 'properties'.
>
> In some cases, the diff turns out to look like we're moving some
> patterns rather than the fixed string properties.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../arm/tegra/nvidia,tegra20-pmc.yaml | 54 ++++++++--------
> .../bindings/regulator/ti,tps65219.yaml | 14 ++--
> .../bindings/sound/tlv320adcx140.yaml | 64 +++++++++----------
> 3 files changed, 66 insertions(+), 66 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-11-23 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 22:37 Rob Herring
2022-11-22 8:49 ` Krzysztof Kozlowski
2022-11-22 12:11 ` Mark Brown
2022-11-23 0:08 ` Rob Herring [this message]
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=166916210667.828774.15527231190149112577.robh@kernel.org \
--to=robh@kernel.org \
--cc=afd@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerome.neanne@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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
all inboxes | Powered by JetHome®