linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: [GIT PULL] Second Round of Renesas rcar-audmapp Driver Updates for v3.17
Date: Wed, 06 Aug 2014 01:37:58 +0000	[thread overview]
Message-ID: <cover.1407288912.git.horms+renesas@verge.net.au> (raw)

Hi Vinod,

Please consider this second round of Second Round of Renesas rcar-audmapp
driver updates for v3.17.

This pull request is based on the previous round of
such requests, tagged as renesas-rcar-audmapp-for-v3.17,
which you have already pulled.

This change appeared after I let you know that I had no more patches
pending the other day. I do not have any more patches pending at this time.


The following changes since commit caf18c27ddb2fb8ae2a7591b908e7efb7484e459:

  dma: rcar-audmapp: add DT support (2014-07-11 13:35:08 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-rcar-audmapp2-for-v3.17

for you to fetch changes up to 84fd82a23742e2d716a1ccb7ad9ef21165dc30bc:

  dt/bindings: rcar-audmapp: tidyup dmas explanation (2014-08-06 09:57:29 +0900)

----------------------------------------------------------------
Second Round of Renesas rcar-audmapp Driver Updates for v3.17

* Tidyup dmas explanation in bindings documentation

----------------------------------------------------------------
Kuninori Morimoto (1):
      dt/bindings: rcar-audmapp: tidyup dmas explanation

 Documentation/devicetree/bindings/dma/rcar-audmapp.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

             reply	other threads:[~2014-08-06  1:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  1:37 Simon Horman [this message]
2014-08-17  0:43 ` [GIT PULL] Second Round of Renesas rcar-audmapp Driver Updates for v3.17 Simon Horman
2014-08-19 17:22 ` 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=cover.1407288912.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --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 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).