From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, Jon Hunter <jonathanh@nvidia.com>,
Conor Dooley <conor+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-tegra@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH 1/3] dt-bindings: spi: tegra-slink: Convert to json-schema
Date: Wed, 5 Jul 2023 14:38:34 -0600 [thread overview]
Message-ID: <168858951392.1858105.14793065413434279529.robh@kernel.org> (raw)
In-Reply-To: <20230705152603.2514235-1-thierry.reding@gmail.com>
On Wed, 05 Jul 2023 17:26:01 +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Convert the Tegra SLINK bindings from the free-form text format to
> json-schema.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../bindings/spi/nvidia,tegra20-slink.txt | 37 --------
> .../bindings/spi/nvidia,tegra20-slink.yaml | 90 +++++++++++++++++++
> 2 files changed, 90 insertions(+), 37 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
> create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-07-05 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:26 [PATCH 1/3] dt-bindings: spi: tegra-slink: Convert to json-schema Thierry Reding
2023-07-05 15:26 ` [PATCH 2/3] dt-bindings: spi: tegra-sflash: " Thierry Reding
2023-07-05 20:40 ` Rob Herring
2023-07-05 15:26 ` [PATCH 3/3] dt-bindings: spi: Convert Tegra114 SPI " Thierry Reding
2023-07-05 20:42 ` Rob Herring
2023-07-05 20:38 ` Rob Herring [this message]
2023-07-11 22:04 ` [PATCH 1/3] dt-bindings: spi: tegra-slink: Convert " Mark Brown
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=168858951392.1858105.14793065413434279529.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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 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.