From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
linux-mmc@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
Vinod Koul <vinod.koul@intel.com>,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Subject: Re: [PATCH 0/3] mmc: sdhi / tmio: add DT DMA
Date: Sun, 26 May 2013 13:53:23 -0400 [thread overview]
Message-ID: <87fvx9ljak.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1366991239-22602-1-git-send-email-g.liakhovetski@gmx.de> (Guennadi Liakhovetski's message of "Fri, 26 Apr 2013 17:47:16 +0200")
Hi Guennadi,
On Fri, Apr 26 2013, Guennadi Liakhovetski wrote:
> These 3 patches add Device Tree DMA support to the TMIO MMC driver, when
> used on SDHI platforms.
>
> Samuel: these patches touch an mfd header file lightly, I think, it's
> better just to get your ack than to make a separate patch via your tree.
>
> Cc: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
>
> Guennadi Liakhovetski (3):
> mmc: sdhi/tmio: make DMA filter implementation specific
> mmc: sdhi/tmio: switch to using dmaengine_slave_config()
> mmc: sdhi/tmio: add DT DMA support
Looks like this doesn't apply to mmc-next -- if you could prepare
current pull requests for 3.10 and 3.11 for me, I'd really appreciate
it. Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2013-05-26 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 15:47 [PATCH 0/3] mmc: sdhi / tmio: add DT DMA Guennadi Liakhovetski
2013-04-26 15:47 ` [PATCH 1/3] mmc: sdhi/tmio: make DMA filter implementation specific Guennadi Liakhovetski
2013-04-26 15:47 ` [PATCH 2/3] mmc: sdhi/tmio: switch to using dmaengine_slave_config() Guennadi Liakhovetski
2013-04-26 15:47 ` [PATCH 3/3] mmc: sdhi/tmio: add DT DMA support Guennadi Liakhovetski
2013-04-26 16:02 ` [PATCH 0/3] mmc: sdhi / tmio: add DT DMA Samuel Ortiz
2013-04-26 16:16 ` Guennadi Liakhovetski
2013-05-26 17:53 ` Chris Ball [this message]
2013-05-26 17:56 ` Chris Ball
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=87fvx9ljak.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sameo@linux.intel.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