From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/13] dmaengine: imx-dma: merge dma arch code into dmaengine.
Date: Wed, 14 Mar 2012 16:44:54 +0530 [thread overview]
Message-ID: <1331723694.1727.28.camel@vkoul-udesk3> (raw)
In-Reply-To: <CACKLOr0XzE0PZk=k5xQQvOA_5dfBk1mYDVyKCep36=3w7ugwWg@mail.gmail.com>
On Wed, 2012-03-14 at 08:43 +0100, javier Martin wrote:
> On 9 March 2012 18:44, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Mar 09, 2012 at 04:20:36PM +0100, Javier Martin wrote:
> >> The following series have to be applied on top of the following patches:
> >> [PATCH v2 1/2] dmaengine: Add support for MEMCPY for imx-dma.
> >> [PATCH v3 2/2] dmaengine: Add support for multiple descriptors for imx-dma.
> >>
> >> As discussed with Vinod and Sascha, the file 'arch/arm/mach-imx/dma-v1.c'
> >> is deprecated and no new patches are accepted for it.
> >>
> >> This series merges this code into the imx-dma.c dmaengine driver.
> >
> > Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
> >
>
> Vinod,
> I think with Sascha's ack, this series is ready to be merged. It's
> quite important for us that it makes it for 3.4.
>
> Please, don't forget the following patch too, which is meant to be
> applied on top of this series:
>
> [PATCH] dmaengine: i.MX: Add support for interleaved transfers.
>
This is my merge queue which means I will merged it after the cookie
fixes (hate rebasing that series again)
--
~Vinod
next prev parent reply other threads:[~2012-03-14 11:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 15:20 [PATCH v3 00/13] dmaengine: imx-dma: merge dma arch code into dmaengine Javier Martin
2012-03-09 15:20 ` [PATCH v3 01/13] dmaengine: imx-dma: merge old dma-v1.c with imx-dma.c Javier Martin
2012-03-09 15:20 ` [PATCH v3 02/13] dmaengine: imx-dma: remove data member from internal structure Javier Martin
2012-03-09 15:20 ` [PATCH v3 03/13] dmaengine: imx-dma: remove dma_mode member of " Javier Martin
2012-03-09 15:20 ` [PATCH v3 04/13] dmaengine: imx-dma: remove 'imxdma_setup_mem2mem_hw' function Javier Martin
2012-03-09 15:20 ` [PATCH v3 05/13] dmaengine: imx-dma: remove 'imxdma_config_channel_hw' function Javier Martin
2012-03-09 15:20 ` [PATCH v3 06/13] dmaengine: imx-dma: remove 'imxdma_setup_sg_hw' function Javier Martin
2012-03-09 15:20 ` [PATCH v3 07/13] dmaengine: imx-dma: remove sg member from internal structure Javier Martin
2012-03-09 15:20 ` [PATCH v3 08/13] dmaengine: imx-dma: remove 'in_use' field of 'internal' structure Javier Martin
2012-03-09 15:20 ` [PATCH v3 09/13] dmaengine: imx-dma: remove 'resbytes' " Javier Martin
2012-03-09 15:20 ` [PATCH v3 10/13] dmaengine: imx-dma: remove internal structure Javier Martin
2012-03-09 15:20 ` [PATCH v3 11/13] dmaengine: imx-dma: remove unused arg of imxdma_sg_next Javier Martin
2012-03-09 15:20 ` [PATCH v3 12/13] dmaengine: imx-dma: remove 'imx_dmav1_baseaddr' and 'dma_clk' Javier Martin
2012-03-09 15:20 ` [PATCH v3 13/13] dmaengine: imx-dma: use 'dev_dbg' and 'dev_warn' for messages Javier Martin
2012-03-09 17:44 ` [PATCH v3 00/13] dmaengine: imx-dma: merge dma arch code into dmaengine Sascha Hauer
2012-03-14 7:43 ` javier Martin
2012-03-14 11:14 ` Vinod Koul [this message]
2012-03-21 7:49 ` javier Martin
2012-03-21 15:39 ` Vinod Koul
2012-03-22 9:39 ` javier Martin
2012-03-22 14:11 ` javier Martin
2012-03-26 6:03 ` Vinod Koul
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=1331723694.1727.28.camel@vkoul-udesk3 \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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