From: Joel Fernandes <joelf@ti.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: <dmaengine@vger.kernel.org>, Matt Porter <matt@ohporter.com>,
Russell King <linux@arm.linux.org.uk>, Dan Williams <djbw@fb.com>,
Jyri Sarha <jsarha@ti.com>, Lars Peter-Clausen <lars@metafoo.de>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux DaVinci Kernel List
<davinci-linux-open-source@linux.davincidsp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<alsa-devel@alsa-project.org>
Subject: Re: [PATCH 2/3] dma: edma: Add support for Cyclic DMA
Date: Thu, 31 Oct 2013 11:03:47 -0500 [thread overview]
Message-ID: <52727F63.6040703@ti.com> (raw)
In-Reply-To: <20131031141012.GJ18788@intel.com>
On 10/31/2013 09:10 AM, Vinod Koul wrote:
> On Thu, Oct 24, 2013 at 12:57:02PM -0500, Joel Fernandes wrote:
>> Rebased on slave-dma/next branch and reapplied:
> Looks like your MUA caused lines to get wrapped and patch is corrupt, can you
> pls resend again using git-send email. I tried even the patch from
> patchworks but that too failed!
Oops my bad, I ran into wordwrap issues. thanks for pointing this out, fixed my
MUA and wont happen again!
Will rebase/resend through git-send-email
thanks,
-Joel
next prev parent reply other threads:[~2013-10-31 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 23:05 [PATCH 0/3] dma: edma: Add cyclic DMA support Joel Fernandes
2013-09-23 23:05 ` [PATCH 1/3] dma: edma: Split out PaRAM set calculations into its own function Joel Fernandes
2013-10-21 7:26 ` Vinod Koul
2013-09-23 23:05 ` [PATCH 2/3] dma: edma: Add support for Cyclic DMA Joel Fernandes
2013-10-21 6:53 ` Vinod Koul
2013-10-22 15:30 ` Joel Fernandes
2013-10-24 16:38 ` Vinod Koul
2013-10-24 17:57 ` Joel Fernandes
2013-10-31 14:10 ` Vinod Koul
2013-10-31 16:03 ` Joel Fernandes [this message]
2013-09-23 23:05 ` [PATCH 3/3] dma: edma: Increase maximum SG limit to 20 Joel Fernandes
2013-10-21 7:26 ` Vinod Koul
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=52727F63.6040703@ti.com \
--to=joelf@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=djbw@fb.com \
--cc=dmaengine@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=lars@metafoo.de \
--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=matt@ohporter.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