From: Rob Herring <robh@kernel.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Yehuda Yitschak <yehuday@marvell.com>,
Jason Cooper <jason@lakedaemon.net>,
Pawel Moll <pawel.moll@arm.com>,
devicetree@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
Hanna Hawa <hannah@marvell.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Nadav Haklai <nadavh@marvell.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Kumar Gala <galak@codeaurora.org>,
dmaengine@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v4 1/4] dt-bindings: dma: add binding for the Marvell XOR v2 engine
Date: Mon, 20 Jun 2016 08:07:24 -0500 [thread overview]
Message-ID: <20160620130724.GA23860@rob-hp-laptop> (raw)
In-Reply-To: <1466080116-26777-2-git-send-email-thomas.petazzoni@free-electrons.com>
On Thu, Jun 16, 2016 at 02:28:33PM +0200, Thomas Petazzoni wrote:
> This commit adds the Device Tree binding documentation for the Marvell
> XOR v2 engine, which is found on Marvell Armada 7K/8K ARM64 SoCs.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> .../devicetree/bindings/dma/mv-xor-v2.txt | 24 ++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/mv-xor-v2.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-06-20 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 12:28 [PATCH v4 0/4] dmaengine driver for Marvell XOR v2 engine Thomas Petazzoni
[not found] ` <1466080116-26777-1-git-send-email-thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-06-16 12:28 ` [PATCH v4 1/4] dt-bindings: dma: add binding for the " Thomas Petazzoni
2016-06-20 13:07 ` Rob Herring [this message]
2016-06-16 12:28 ` [PATCH v4 2/4] dma: mv_xor_v2: new driver Thomas Petazzoni
2016-06-16 12:28 ` [PATCH v4 3/4] arm64: dts: marvell: adjust to the latest mv-xor-v2 DT binding Thomas Petazzoni
[not found] ` <1466080116-26777-4-git-send-email-thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-06-30 11:50 ` Gregory CLEMENT
2016-06-16 12:28 ` [PATCH v4 4/4] arm64: dts: marvell: add XOR engine description for Armada 7K/8K CP Thomas Petazzoni
[not found] ` <1466080116-26777-5-git-send-email-thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-06-30 11:50 ` Gregory CLEMENT
2016-06-28 14:38 ` [PATCH v4 0/4] dmaengine driver for Marvell XOR v2 engine Vinod Koul
2016-06-28 14:37 ` Thomas Petazzoni
2016-07-07 20:42 ` Thomas Petazzoni
[not found] ` <20160707224248.71511ecd-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-07-12 4:42 ` Vinod Koul
2016-07-12 7:10 ` Thomas Petazzoni
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=20160620130724.GA23860@rob-hp-laptop \
--to=robh@kernel.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregory.clement@free-electrons.com \
--cc=hannah@marvell.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nadavh@marvell.com \
--cc=pawel.moll@arm.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vinod.koul@intel.com \
--cc=yehuday@marvell.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