From: Vinod <vkoul@kernel.org>
To: Wen He <wen.he_1@nxp.com>
Cc: dmaengine@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, leoyang.li@nxp.com,
jiafei.pan@nxp.com, jiaheng.fan@nxp.com
Subject: Re: [v5 1/6] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT
Date: Tue, 29 May 2018 10:19:25 +0530 [thread overview]
Message-ID: <20180529044925.GD5666@vkoul-mobl> (raw)
In-Reply-To: <20180525111920.24498-1-wen.he_1@nxp.com>
On 25-05-18, 19:19, Wen He wrote:
> This patch implenment a standard macro call functions is
> used to NXP dma drivers.
Well that patch seems to do a bit more than replace DMA_IN/OUT by FSL_DMA_IN/OUT
care to explain those. best would be to do a patch which does replace and then
add new things in separate patch, easier to review
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Wen He <wen.he_1@nxp.com>
Cc: dmaengine@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, leoyang.li@nxp.com,
jiafei.pan@nxp.com, jiaheng.fan@nxp.com
Subject: [v5,1/6] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT
Date: Tue, 29 May 2018 10:19:25 +0530 [thread overview]
Message-ID: <20180529044925.GD5666@vkoul-mobl> (raw)
On 25-05-18, 19:19, Wen He wrote:
> This patch implenment a standard macro call functions is
> used to NXP dma drivers.
Well that patch seems to do a bit more than replace DMA_IN/OUT by FSL_DMA_IN/OUT
care to explain those. best would be to do a patch which does replace and then
add new things in separate patch, easier to review
next prev parent reply other threads:[~2018-05-29 4:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 11:19 [v5 1/6] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Wen He
2018-05-25 11:19 ` [v5,1/6] " Wen He
2018-05-25 11:19 ` [v5 2/6] dmaengine: fsl-qdma: Add qDMA controller driver for Layerscape SoCs Wen He
2018-05-25 11:19 ` [v5,2/6] " Wen He
2018-05-29 7:07 ` [v5 2/6] " Vinod
2018-05-29 7:07 ` [v5,2/6] " Vinod Koul
2018-05-29 9:59 ` [v5 2/6] " Wen He
2018-05-29 9:59 ` [v5,2/6] " Wen He
2018-05-29 10:19 ` [v5 2/6] " Vinod
2018-05-29 10:19 ` [v5,2/6] " Vinod Koul
2018-05-29 10:38 ` [v5 2/6] " Wen He
2018-05-29 10:38 ` [v5,2/6] " Wen He
2018-05-30 10:27 ` [v5 2/6] " Vinod Koul
2018-05-30 10:27 ` [v5,2/6] " Vinod Koul
2018-05-31 1:58 ` [v5 2/6] " Wen He
2018-05-31 1:58 ` [v5,2/6] " Wen He
2018-06-05 16:28 ` [v5 2/6] " Vinod
2018-06-05 16:28 ` [v5,2/6] " Vinod Koul
2018-06-11 8:14 ` [v5 2/6] " Wen He
2018-06-11 8:14 ` [v5,2/6] " Wen He
2018-06-14 2:15 ` [v5 2/6] " Wen He
2018-06-14 2:15 ` [v5,2/6] " Wen He
2018-06-14 7:26 ` [v5 2/6] " Vinod
2018-06-14 7:26 ` [v5,2/6] " Vinod Koul
2018-05-30 18:51 ` [v5 2/6] " Li Yang
2018-05-30 18:51 ` [v5,2/6] " Li Yang
2018-06-04 9:53 ` [v5 2/6] " Wen He
2018-06-04 9:53 ` [v5,2/6] " Wen He
2018-06-05 16:30 ` [v5 2/6] " Vinod
2018-06-05 16:30 ` [v5,2/6] " Vinod Koul
2018-06-05 17:24 ` [v5 2/6] " Li Yang
2018-06-05 17:24 ` [v5,2/6] " Li Yang
2018-06-12 4:00 ` [v5 2/6] " Vinod
2018-06-12 4:00 ` [v5,2/6] " Vinod Koul
2018-06-12 16:32 ` [v5 2/6] " Li Yang
2018-06-12 16:32 ` [v5,2/6] " Li Yang
2018-05-25 11:19 ` [v5 3/6] dt-bindings: fsl-qdma: Add NXP Layerscpae qDMA controller bindings Wen He
2018-05-25 11:19 ` [v5,3/6] " Wen He
2018-05-31 0:49 ` [v5 3/6] " Rob Herring
2018-05-31 0:49 ` [v5,3/6] " Rob Herring
2018-05-25 11:19 ` [v5 4/6] arm64: dts: ls1043a: add qdma device tree nodes Wen He
2018-05-25 11:19 ` [v5,4/6] " Wen He
2018-05-25 11:19 ` [v5 5/6] arm64: dts: ls1046a: " Wen He
2018-05-25 11:19 ` [v5,5/6] " Wen He
2018-05-25 11:19 ` [v5 6/6] arm: dts: ls1021a: " Wen He
2018-05-25 11:19 ` [v5,6/6] " Wen He
2018-05-29 4:49 ` Vinod [this message]
2018-05-29 4:49 ` [v5,1/6] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Vinod Koul
2018-05-29 10:14 ` [v5 1/6] " Wen He
2018-05-29 10:14 ` [v5,1/6] " Wen He
2018-05-29 10:21 ` [v5 1/6] " Vinod
2018-05-29 10:21 ` [v5,1/6] " Vinod Koul
2018-05-29 10:22 ` [v5 1/6] " Wen He
2018-05-29 10:22 ` [v5,1/6] " Wen He
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=20180529044925.GD5666@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jiafei.pan@nxp.com \
--cc=jiaheng.fan@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=robh+dt@kernel.org \
--cc=wen.he_1@nxp.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.