From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-arm-kernel@lists.infradead.org,
Peter Meerwald <pmeerw@pmeerw.net>, Dan Williams <djbw@fb.com>,
linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: [RFC v2] dmaengine: omap-dma: Start DMA without delay for cyclic channels
Date: Tue, 9 Apr 2013 12:20:17 +0200 [thread overview]
Message-ID: <5163EB61.3000507@ti.com> (raw)
In-Reply-To: <20130409072600.GA31193@intel.com>
On 04/09/2013 09:26 AM, Vinod Koul wrote:
> Yes it should go thru dmaengine tree, sorry was travelling hence the delay, pls
> resend the patch and I will do the needful
I already have the patch rebased on today's linux-next, just waiting for
Russell to confirm that I can add his Acked-by to the patch.
I take this from Russell as ACK: "Now that I'm back from a short 4 day break,
then yes, and the answer is that it's fine. Who's handling the patch?"
But I want to be sure I can add that line...
--
Péter
next prev parent reply other threads:[~2013-04-09 10:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 11:17 [RFC v2] dmaengine: omap-dma: Start DMA without delay for cyclic channels Peter Ujfalusi
2013-04-03 11:24 ` Santosh Shilimkar
2013-04-03 11:52 ` Peter Ujfalusi
2013-04-03 12:00 ` Santosh Shilimkar
2013-04-08 7:11 ` Peter Ujfalusi
2013-04-08 17:09 ` Russell King - ARM Linux
2013-04-08 17:15 ` Tony Lindgren
2013-04-09 6:52 ` Santosh Shilimkar
2013-04-09 7:19 ` Peter Ujfalusi
2013-04-09 7:26 ` Vinod Koul
2013-04-09 10:20 ` Peter Ujfalusi [this message]
2013-04-09 7:19 ` Peter Ujfalusi
2013-04-09 7:21 ` Peter Ujfalusi
2013-04-09 13:54 ` Russell King - ARM Linux
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=5163EB61.3000507@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=balbi@ti.com \
--cc=djbw@fb.com \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pmeerw@pmeerw.net \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).