From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Vinod Koul <vkoul@kernel.org>,
linux-riscv@lists.infradead.org,
Alexandre Ghiti <alexandre.ghiti@canonical.com>,
Palmer Debbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, Green Wan <green.wan@sifive.com>,
Rob Herring <robh+dt@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: dmaengine: sifive,fu540-c000: include generic schema
Date: Mon, 21 Mar 2022 13:55:18 -0500 [thread overview]
Message-ID: <YjjKFvNZ1BVn/zaB@robh.at.kernel.org> (raw)
In-Reply-To: <20220318162044.169350-1-krzysztof.kozlowski@canonical.com>
On Fri, 18 Mar 2022 17:20:43 +0100, Krzysztof Kozlowski wrote:
> Include generic dma-controller.yaml schema, which enforces node naming
> and other generic properties.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../devicetree/bindings/dma/sifive,fu540-c000-pdma.yaml | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-03-21 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:20 [PATCH 1/2] dt-bindings: dmaengine: sifive,fu540-c000: include generic schema Krzysztof Kozlowski
2022-03-18 16:20 ` [PATCH 2/2] riscv: dts: sifive: fu540-c000: align dma node name with dtschema Krzysztof Kozlowski
2022-04-19 10:09 ` Krzysztof Kozlowski
2022-04-19 10:45 ` Conor.Dooley
2022-04-19 10:50 ` Krzysztof Kozlowski
2022-04-19 10:57 ` Conor.Dooley
2022-04-19 10:59 ` Krzysztof Kozlowski
2022-04-19 12:18 ` Zong Li
2022-03-21 18:55 ` 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=YjjKFvNZ1BVn/zaB@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.ghiti@canonical.com \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=green.wan@sifive.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--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 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).