From: Daniel Mack <zonque@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org, kishon@ti.com
Subject: Re: [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case
Date: Thu, 17 Oct 2013 16:23:32 +0200 [thread overview]
Message-ID: <525FF2E4.8030304@gmail.com> (raw)
In-Reply-To: <525FF234.8010105@linutronix.de>
On 10/17/2013 04:20 PM, Sebastian Andrzej Siewior wrote:
> On 10/17/2013 04:19 PM, Sebastian Andrzej Siewior wrote:
>> This patch changes the logic here to look on both queues for the
>> descriptor.
>
> Daniel, could please look if this solves your suspend / resume warnings?
Will do (hopefully) tomorrow. So this is a replacement for my "dma:
cppi41: move -EAGAIN in tear_down" patch, or does it go on top of it?
How does your patch queue look like? Someone should probably re-collect
all necessary patches for the next merge window eventually, so Vinod
knows what to apply :)
Thanks,
Daniel
next prev parent reply other threads:[~2013-10-17 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 14:19 [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case Sebastian Andrzej Siewior
2013-10-17 14:19 ` [PATCH 2/2] dma: cppi41: return code > 0 of pm_runtime_get_sync() is not an error Sebastian Andrzej Siewior
2013-10-17 14:20 ` [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case Sebastian Andrzej Siewior
2013-10-17 14:23 ` Daniel Mack [this message]
2013-10-17 14:36 ` Sebastian Andrzej Siewior
[not found] ` <5260F961.1000308@gmail.com>
2013-10-28 11:10 ` Daniel Mack
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=525FF2E4.8030304@gmail.com \
--to=zonque@gmail.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dan.j.williams@intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vinod.koul@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 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.