From: Thierry Reding <thierry.reding@gmail.com>
To: Sameer Pujar <spujar@nvidia.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
jonathanh@nvidia.com, vkoul@kernel.org, tglx@linutronix.de,
jason@lakedaemon.net, maz@kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: dma: Convert ADMA doc to json-schema
Date: Tue, 10 Nov 2020 20:46:47 +0100 [thread overview]
Message-ID: <20201110194647.GD2375022@ulmo> (raw)
In-Reply-To: <1604677413-20411-3-git-send-email-spujar@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Fri, Nov 06, 2020 at 09:13:31PM +0530, Sameer Pujar wrote:
> Move ADMA documentation to YAML format.
>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
> .../bindings/dma/nvidia,tegra210-adma.txt | 56 ------------
> .../bindings/dma/nvidia,tegra210-adma.yaml | 99 ++++++++++++++++++++++
> 2 files changed, 99 insertions(+), 56 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.txt
> create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-10 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:43 [PATCH v2 0/4] Convert few Tegra docs to json-schema Sameer Pujar
2020-11-06 15:43 ` [PATCH v2 1/4] arm64: tegra: Rename ADMA device nodes for Tegra210 Sameer Pujar
2020-11-10 19:44 ` Thierry Reding
2020-11-06 15:43 ` [PATCH v2 2/4] dt-bindings: dma: Convert ADMA doc to json-schema Sameer Pujar
2020-11-09 21:45 ` Rob Herring
2020-11-10 19:46 ` Thierry Reding [this message]
2020-11-06 15:43 ` [PATCH v2 3/4] dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles Sameer Pujar
2020-11-06 15:43 ` [PATCH v2 4/4] dt-bindings: bus: Convert ACONNECT doc to json-schema Sameer Pujar
2020-11-09 21:45 ` 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=20201110194647.GD2375022@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--cc=tglx@linutronix.de \
--cc=vkoul@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.