From: Vinod Koul <vinod.koul@intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Lee Jones" <lee.jones@linaro.org>,
dmaengine@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Subject: Re: [PATCH] dmaengine: use phys_addr_t for slave configuration
Date: Mon, 15 Feb 2016 23:00:53 +0530 [thread overview]
Message-ID: <20160215173053.GM19598@localhost> (raw)
In-Reply-To: <20160209225724.GA1522@katana>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Tue, Feb 09, 2016 at 11:57:24PM +0100, Wolfram Sang wrote:
>
> > This is a dependency for adding iommu support to the rcar-dmac driver, cfr.
> > "[PATCH v2 0/5] dmaengine: rcar-dmac: add iommu support for slave transfers".
> > http://www.spinics.net/lists/linux-renesas-soc/msg00066.html
> > https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg00108.html
> >
> > Thank you for applying!
>
> Yup, we really need it. Anything we can do to help?
I have done this change and discussing wider changes
I will send CFT hopefully before EOW, pls test :)
--
~Vinod
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-15 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 9:06 [PATCH] dmaengine: use phys_addr_t for slave configuration Linus Walleij
2013-04-26 9:14 ` Lee Jones
2013-04-26 9:40 ` Arnd Bergmann
2015-07-08 10:12 ` Geert Uytterhoeven
2015-07-10 8:14 ` Vinod Koul
2015-12-15 10:48 ` Geert Uytterhoeven
2015-12-15 17:26 ` Vinod Koul
2016-02-03 11:17 ` Geert Uytterhoeven
2016-02-09 22:57 ` Wolfram Sang
2016-02-15 17:30 ` Vinod Koul [this message]
2016-02-15 17:34 ` Wolfram Sang
2016-02-16 20:42 ` Niklas Söderlund
2015-07-16 9:22 ` Linus Walleij
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=20160215173053.GM19598@localhost \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=wsa@the-dreams.de \
/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