[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090325.184215.229418774.nemoto@toshiba-tops.co.jp>
Date: Wed, 25 Mar 2009 18:42:15 +0900 (JST)
From: Atsushi Nemoto <anemo@....ocn.ne.jp>
To: dan.j.williams@...el.com
Cc: maciej.sosnowski@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dmaengine: Add privatecnt to revert DMA_PRIVATE propery
On Mon, 16 Mar 2009 13:39:49 -0700, Dan Williams <dan.j.williams@...el.com> wrote:
> > Currently dma_request_channel() set DMA_PRIVATE capability but never
> > clear it. So if a public channel was once grabbed by
> > dma_request_channel(), the device stay PRIVATE forever. Add
> > privatecnt member to dma_device to correctly revert it.
> >
> > Signed-off-by: Atsushi Nemoto <anemo@....ocn.ne.jp>
> > ---
>
> This looks good to me. Please rebase it on top of the 'next' branch
> of the async_tx tree[1] and I will queue it for -next.
>
> Thanks,
> Dan
>
> http://git.kernel.org/?p=linux/kernel/git/djbw/async_tx.git;a=shortlog;h=next
Sorry, I have missed this mail. I will rebase it, but while the
'next' branch of async_tx tree lacks commit 287d85 ("atmel-mci: fix
initialization of dma slave data"), rebasing will cause another
conflict with mainline. What should I do?
---
Atsushi Nemoto
--
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