From: Vinod Koul <vinod.koul@linux.intel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7 v2] dma: sh: stop using .private
Date: Fri, 20 Jul 2012 06:12:28 +0000 [thread overview]
Message-ID: <1342764028.1726.195.camel@vkoul-udesk3> (raw)
In-Reply-To: <1341484183-10757-1-git-send-email-g.liakhovetski@gmx.de>
On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> This patch series supersedes the one from yesterday with the same title.
> The 4 patches from v1 are all unchanged, v2 just prepends them with 3 more
> preparatory patches. From the original series description:
>
> Here's an attempt to convert the shdma driver to a new method, whereby a
> centrally provided filter function is used and the DMA_SLAVE_CONFIG command
> is enabled for slave operation. The last patch is an illustration of how
> this new method shall be used. If this approach is acceptable, I'll also
> convert the remaining shdma user drivers. This patch series goes on top of
> my earlier patches to split shdma.c.
Applied thanks.
Fixed one checkpatch issue though!!
ERROR: "(foo*)" should be "(foo *)"
#996: FILE: drivers/dma/sh/shdma-base.c:662:
+ config = (struct dma_slave_config*)arg;
Please *always* run checkpatch on the patches you send
--
~Vinod
prev parent reply other threads:[~2012-07-20 6:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 10:29 [PATCH 0/7 v2] dma: sh: stop using .private Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 1/7 v2] dmaengine: shdma: (cosmetic) simplify a static function Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 2/7 v2] ASoC: siu: don't use DMA device for channel filtering Guennadi Liakhovetski
2012-07-05 12:08 ` Mark Brown
2012-07-05 13:54 ` Guennadi Liakhovetski
2012-07-05 14:00 ` Mark Brown
2012-07-05 14:08 ` Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 3/7 v2] sh: remove unused DMA device pointer from SIU platform data Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 4/7 v2] dmaengine: shdma: prepare to stop using struct dma_chan::private Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 5/7 v2] dma: sh: use an integer slave ID to improve API compatibility Guennadi Liakhovetski
2012-07-16 6:19 ` Vinod Koul
2012-07-16 6:37 ` Guennadi Liakhovetski
2012-07-16 6:57 ` Vinod Koul
2012-07-16 7:13 ` Guennadi Liakhovetski
2012-07-16 8:40 ` Vinod Koul
2012-07-16 8:47 ` Guennadi Liakhovetski
2012-07-16 9:49 ` Vinod Koul
2012-07-16 10:01 ` Guennadi Liakhovetski
2012-07-16 10:36 ` Vinod Koul
2012-07-16 10:55 ` Guennadi Liakhovetski
2012-07-16 11:24 ` Vinod Koul
2012-07-16 12:47 ` Guennadi Liakhovetski
2012-07-18 3:26 ` Vinod Koul
2012-07-18 8:34 ` Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 6/7 v2] dma: sh: provide a migration path for slave drivers to stop using .private Guennadi Liakhovetski
2012-07-16 6:31 ` Vinod Koul
2012-07-16 6:31 ` Guennadi Liakhovetski
2012-07-05 10:29 ` [PATCH 7/7 v2] mmc: sh_mmcif: switch to the new DMA channel allocation and configuration Guennadi Liakhovetski
2012-07-20 6:12 ` 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=1342764028.1726.195.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).