From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: vkoul@kernel.org, dan.j.williams@intel.com, afaerber@suse.de,
dmaengine@vger.kernel.org, liuwei@actions-semi.com,
96boards@ucrobotics.com, devicetree@vger.kernel.org,
daniel.thompson@linaro.org, amit.kucheria@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, hzhang@ucrobotics.com,
bdong@ucrobotics.com, manivannanece23@gmail.com,
thomas.liau@actions-semi.com, jeff.chen@actions-semi.com,
pn@denx.de, edgar.righi@lsitec.org.br
Subject: Re: [PATCH v3 1/4] dt-bindings: dmaengine: Add binding for Actions Semi Owl SoCs
Date: Mon, 30 Jul 2018 17:10:37 -0600 [thread overview]
Message-ID: <20180730231037.GA2265@rob-hp-laptop> (raw)
In-Reply-To: <20180726050658.1399-2-manivannan.sadhasivam@linaro.org>
On Thu, Jul 26, 2018 at 10:36:55AM +0530, Manivannan Sadhasivam wrote:
> Add devicetree binding for Actions Semi Owl SoCs DMA controller.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> .../devicetree/bindings/dma/owl-dma.txt | 47 +++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/owl-dma.txt
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-07-30 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 5:06 [PATCH v3 0/4] Add Actions Semi Owl family S900 DMA Controller support Manivannan Sadhasivam
2018-07-26 5:06 ` [PATCH v3 1/4] dt-bindings: dmaengine: Add binding for Actions Semi Owl SoCs Manivannan Sadhasivam
2018-07-30 23:10 ` Rob Herring [this message]
2018-08-09 2:46 ` Vinod
2018-07-26 5:06 ` [PATCH v3 2/4] arm64: dts: actions: Add Actions Semi S900 DMA Controller Manivannan Sadhasivam
2018-07-26 5:06 ` [PATCH v3 3/4] dmaengine: Add Actions Semi Owl family S900 DMA driver Manivannan Sadhasivam
2018-08-09 2:46 ` Vinod
2018-07-26 5:06 ` [PATCH v3 4/4] MAINTAINERS: Add entry for Actions Semi Owl SoCs " Manivannan Sadhasivam
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=20180730231037.GA2265@rob-hp-laptop \
--to=robh@kernel.org \
--cc=96boards@ucrobotics.com \
--cc=afaerber@suse.de \
--cc=amit.kucheria@linaro.org \
--cc=bdong@ucrobotics.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=edgar.righi@lsitec.org.br \
--cc=hzhang@ucrobotics.com \
--cc=jeff.chen@actions-semi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwei@actions-semi.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=manivannanece23@gmail.com \
--cc=pn@denx.de \
--cc=thomas.liau@actions-semi.com \
--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