From: Vinod Koul <vinod.koul@intel.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
dmaengine@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
devicetree@vger.kernel.org
Subject: [v4] dmaengine: rcar-dmac: Document R-Car D3 bindings
Date: Sat, 28 Apr 2018 10:44:01 +0530 [thread overview]
Message-ID: <20180428051401.GI6014@localhost> (raw)
On Tue, Apr 24, 2018 at 10:51:06AM +0200, Simon Horman wrote:
> From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
>
> R8A77995's SYS-DMAC is R-Car Gen3-compatible.
Applied, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
dmaengine@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dmaengine: rcar-dmac: Document R-Car D3 bindings
Date: Sat, 28 Apr 2018 10:44:01 +0530 [thread overview]
Message-ID: <20180428051401.GI6014@localhost> (raw)
In-Reply-To: <20180424085106.11907-1-horms+renesas@verge.net.au>
On Tue, Apr 24, 2018 at 10:51:06AM +0200, Simon Horman wrote:
> From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
>
> R8A77995's SYS-DMAC is R-Car Gen3-compatible.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-04-28 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 5:14 Vinod Koul [this message]
2018-04-28 5:14 ` [PATCH v4] dmaengine: rcar-dmac: Document R-Car D3 bindings Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-04-27 14:31 [v4] " Rob Herring
2018-04-27 14:31 ` [PATCH v4] " Rob Herring
2018-04-24 8:51 [v4] " Simon Horman
2018-04-24 8:51 ` [PATCH v4] " Simon Horman
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=20180428051401.GI6014@localhost \
--to=vinod.koul@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ulrich.hecht+renesas@gmail.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 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.