[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1332741833.19804.17.camel@vkoul-udesk3>
Date: Mon, 26 Mar 2012 11:33:53 +0530
From: Vinod Koul <vinod.koul@...ux.intel.com>
To: javier Martin <javier.martin@...ta-silicon.com>
Cc: kernel@...gutronix.de, dan.j.williams@...el.com,
linux@....linux.org.uk, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 00/13] dmaengine: imx-dma: merge dma arch code into
dmaengine.
On Thu, 2012-03-22 at 15:11 +0100, javier Martin wrote:
> On 22 March 2012 10:39, javier Martin <javier.martin@...ta-silicon.com> wrote:
> > On 21 March 2012 16:39, Vinod Koul <vinod.koul@...ux.intel.com> wrote:
> >> This doesn't apply for me (starting with 6th) on current slave-dma.next
> >> due to obvious changes which have gone into imx.
> >>
> >> Can you quickly rebase the series and resend.
> >
> > Great,
> > now your 'next' branch is actually broken for imx-dma.
> >
> > I'm currently trying a bisect to find out what is the commit
> > responsible for that but I suspect it will be related to the cookie
> > changes submitted by Russell.
I had these in branch for quite some time for people to look and point
out any issues with merge.
>
> Here,
> take a look at this series:
>
> [PATCH v4 00/15] dmaengine: imx-dma: rebase of features for 3.4.
>
> I've included a new fix patch which solves the merge issue.
Thanks Applied all, now
>
> Regards.
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists