public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel•com>
To: Alexander Popov <a13xp0p0v88@gmail•com>
Cc: Mark Rutland <mark.rutland@arm•com>,
	devicetree@vger•kernel.org, Lars-Peter Clausen <lars@metafoo•de>,
	Arnd Bergmann <arnd@arndb•de>, Gerhard Sittig <gsi@denx•de>,
	Andy Shevchenko <andriy.shevchenko@linux•jf.intel.com>,
	dmaengine@vger•kernel.org,
	Dan Williams <dan.j.williams@intel•com>,
	Anatolij Gustschin <agust@denx•de>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v3 0/3] dmaengine: mpc512x: add device tree binding document and DMA channel lookup
Date: Fri, 25 Jul 2014 19:55:59 +0530	[thread overview]
Message-ID: <20140725142559.GU8181@intel.com> (raw)
In-Reply-To: <1403693580-9449-1-git-send-email-a13xp0p0v88@gmail.com>

On Wed, Jun 25, 2014 at 02:52:57PM +0400, Alexander Popov wrote:
> This patch series introduces a device tree binding document for
> the MPC512x DMA controller and adds device tree based DMA channel lookup
> for it.
> 
> This version contains the improved device tree binding document:
> #dma-cells is made a required property, as it must be according
> dma/dma.txt document.

Applied, thanks

-- 
~Vinod

      parent reply	other threads:[~2014-07-25 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 10:52 [PATCH v3 0/3] dmaengine: mpc512x: add device tree binding document and DMA channel lookup Alexander Popov
2014-06-25 10:52 ` [PATCH v3 1/3] dmaengine: mpc512x: add device tree binding document Alexander Popov
2014-06-25 10:52 ` [PATCH v3 2/3] dmaengine: of: add common xlate function for matching by channel id Alexander Popov
2014-06-25 10:53 ` [PATCH v3 3/3] dmaengine: mpc512x: register for device tree channel lookup Alexander Popov
2014-07-20 19:18 ` [PATCH v3 0/3] dmaengine: mpc512x: add device tree binding document and DMA " Alexander Popov
2014-07-25 14:25 ` 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=20140725142559.GU8181@intel.com \
    --to=vinod.koul@intel$(echo .)com \
    --cc=a13xp0p0v88@gmail$(echo .)com \
    --cc=agust@denx$(echo .)de \
    --cc=andriy.shevchenko@linux$(echo .)jf.intel.com \
    --cc=arnd@arndb$(echo .)de \
    --cc=dan.j.williams@intel$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dmaengine@vger$(echo .)kernel.org \
    --cc=gsi@denx$(echo .)de \
    --cc=lars@metafoo$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mark.rutland@arm$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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