public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Linus <torvalds@linux-foundation.org>
Cc: Dan Williams <djbw@fb.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"arnd@arndb.de" <ArndBergmann@intel.com>,
	Matt Porter <mporter@ti.com>
Subject: [GIT PULL] slave-dmaengine updates 2
Date: Fri, 1 Mar 2013 10:36:28 +0530	[thread overview]
Message-ID: <20130301050628.GD28537@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hi Linus,

Here is my second pull request for this merge window.

The Arnd's patch moves the dw_dmac to use generic DMA binding. I agreed to merge
this late as it will avoid the conflicts between tree's.

The second patch from Matt adding a  dma_request_slave_channel_compat API was
supposed to be picked up, but somehow never got picked up.  Some patches
dependent on this are already in -next :(

Thanks
~Vinod

The following changes since commit 17166a3b6e88b93189e6be5f7e1335a3cc4fa965:
are available in the git repository at:

  git://git.infradead.org/users/vkoul/slave-dma.git next

Arnd Bergmann (1):
      dmaengine: dw_dmac: move to generic DMA binding

Matt Porter (1):
      dmaengine: add dma_request_slave_channel_compat()

 Documentation/devicetree/bindings/dma/snps-dma.txt |   70 +++++-----
 drivers/dma/dw_dmac.c                              |  145 ++++++++++----------
 drivers/dma/dw_dmac_regs.h                         |    7 +-
 include/linux/dmaengine.h                          |   16 ++
 include/linux/dw_dmac.h                            |    5 -
 5 files changed, 127 insertions(+), 116 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2013-03-01  5:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130301050628.GD28537@intel.com \
    --to=vinod.koul@intel.com \
    --cc=ArndBergmann@intel.com \
    --cc=djbw@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mporter@ti.com \
    --cc=torvalds@linux-foundation.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