From: Vinod Koul <vinod.koul@intel.com>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 0/8 v4] bcm2835 DMA slave support
Date: Tue, 5 Apr 2016 11:03:53 -0700 [thread overview]
Message-ID: <20160405180352.GA8930@vkoul-mobl.iind.intel.com> (raw)
In-Reply-To: <1458156302-4359-1-git-send-email-eric@anholt.net>
On Wed, Mar 16, 2016 at 12:24:54PM -0700, Eric Anholt wrote:
> Here's the series for DMA slave and memcpy support for 2835, with the
> DT changes to enable the remaining channels dropped out while that
> goes through review. I had to do some minor conflict resolution, but
> it was pretty mechanical, and I tested again with dmatest on the last
> patch.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-04-05 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 19:24 [PATCH 0/8 v4] bcm2835 DMA slave support Eric Anholt
2016-03-16 19:24 ` [PATCH 1/8] dmaengine: bcm2835: set residue_granularity field Eric Anholt
2016-03-16 19:24 ` [PATCH 2/8] dmaengine: bcm2835: remove unnecessary masking of dma channels Eric Anholt
2016-03-16 19:24 ` [PATCH 3/8] dmaengine: bcm2835: add additional defines for DMA-registers Eric Anholt
2016-03-16 19:24 ` [PATCH 4/8] dmaengine: bcm2835: move cyclic member from bcm2835_chan into bcm2835_desc Eric Anholt
2016-03-16 19:24 ` [PATCH 5/8] dmaengine: bcm2835: move controlblock chain generation into separate method Eric Anholt
2016-03-16 19:25 ` [PATCH 6/8] dmaengine: bcm2835: limit max length based on channel type Eric Anholt
2016-03-16 19:25 ` [PATCH 7/8] dmaengine: bcm2835: add slave_sg support to bcm2835-dma Eric Anholt
2016-03-16 19:25 ` [PATCH 8/8] dmaengine: bcm2835: add dma_memcopy " Eric Anholt
2016-03-17 10:22 ` [PATCH 0/8 v4] bcm2835 DMA slave support Martin Sperl
2016-03-17 13:17 ` Martin Sperl
2016-04-05 18:03 ` Vinod Koul [this message]
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=20160405180352.GA8930@vkoul-mobl.iind.intel.com \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.org \
/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