mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: maciej.sosnowski@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: Add privatecnt to revert DMA_PRIVATE propery
Date: Wed, 25 Mar 2009 09:27:27 -0700	[thread overview]
Message-ID: <e9c3a7c20903250927iea1a4b1h1041deee251e4e5f@mail.gmail.com> (raw)
In-Reply-To: <20090325.184215.229418774.nemoto@toshiba-tops.co.jp>

On Wed, Mar 25, 2009 at 2:42 AM, Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> On Mon, 16 Mar 2009 13:39:49 -0700, Dan Williams <dan.j.williams@intel.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@mba.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?

I have updated the 'next' branch to include this commit.

Thanks,
Dan

  reply	other threads:[~2009-03-25 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 11:07 Atsushi Nemoto
2009-03-11  8:34 ` Sosnowski, Maciej
2009-03-16 20:39 ` Dan Williams
2009-03-25  9:42   ` Atsushi Nemoto
2009-03-25 16:27     ` Dan Williams [this message]
2009-03-26 11:44       ` Atsushi Nemoto
2009-03-26 17:02         ` Dan Williams

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=e9c3a7c20903250927iea1a4b1h1041deee251e4e5f@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.sosnowski@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®