From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [GIT PULL FOR v3.20] R-Car DMA engine driver
Date: Wed, 24 Dec 2014 05:47:44 +0000 [thread overview]
Message-ID: <20141224053544.GT16827@intel.com> (raw)
In-Reply-To: <25808042.z3ylOLx5GF@avalon>
On Tue, Dec 23, 2014 at 11:16:52AM +0200, Laurent Pinchart wrote:
> Hi Vinod,
>
> The following changes since commit fbde286783f7c1e55e6c33575fa1a56f8ea77c90:
>
> dmaengine: nbpfaxi: update the driver comments (2014-12-22 20:28:04 +0530)
>
> are available in the git repository at:
>
> git://linuxtv.org/pinchartl/fbdev.git dma/next
>
> for you to fetch changes up to ee4b876bbee2c5c53518110849f23c117eec099c:
>
> dmaengine: rcar-dmac: Handle hardware descriptor allocation failure
> (2014-12-23 11:13:03 +0200)
Merged now, Thanks
--
~Vinod
>
> ----------------------------------------------------------------
> Jürg Billeter (1):
> dmaengine: rcar-dmac: Handle hardware descriptor allocation failure
>
> Laurent Pinchart (5):
> dmaengine: Add 16 bytes, 32 bytes and 64 bytes bus widths
> dmaengine: rcar-dmac: Remove duplicate sentence from DT bindings
> dmaengine: rcar-dmac: Add Renesas R-Car Gen2 DMA Controller (DMAC)
> driver
> dmaengine: rcar-dmac: Implement support for hardware descriptor lists
> dmaengine: rcar-dmac: Cache hardware descriptors memory
>
> .../devicetree/bindings/dma/renesas,rcar-dmac.txt | 3 -
> drivers/dma/Makefile | 2 +-
> drivers/dma/sh/Kconfig | 14 +-
> drivers/dma/sh/Makefile | 1 +
> drivers/dma/sh/rcar-dmac.c | 1747 ++++++++++++++
> include/linux/dmaengine.h | 3 +
> 6 files changed, 1765 insertions(+), 5 deletions(-)
> create mode 100644 drivers/dma/sh/rcar-dmac.c
>
> --
> Regards,
>
> Laurent Pinchart
>
--
next prev parent reply other threads:[~2014-12-24 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 9:16 [GIT PULL FOR v3.20] R-Car DMA engine driver Laurent Pinchart
2014-12-24 5:47 ` Vinod Koul [this message]
2015-01-19 10:30 ` Geert Uytterhoeven
2015-01-19 13:41 ` Geert Uytterhoeven
2015-01-19 13:44 ` Vinod Koul
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=20141224053544.GT16827@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.