From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
Srikanth Vemula <svemula@xilinx.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srikanth Thokala <sthokal@xilinx.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Michal Simek <michals@xilinx.com>,
Anirudha Sarangi <anirudh@xilinx.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: Re: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support
Date: Tue, 21 Oct 2014 11:14:55 +0200 [thread overview]
Message-ID: <3236720.MHeqOodrCV@wuerfel> (raw)
In-Reply-To: <ff137744d6474640aab09e5d6f62921a@BN1AFFO11FD019.protection.gbl>
On Tuesday 21 October 2014 09:06:13 Appana Durga Kedareswara Rao wrote:
> The above mentioned API's and structures will be used by the dma test
> client driver's to set hardware configuration information. The dma
> client drivers are not mainlined yet and it is
> Internally used by our git-tree to test the DMA functionality in loopback .
I would suggest you add the test driver into the main dmaengine driver
file directly then, so you don't need to export the symbols. If there
are important reasons to keep that as separate files, just move the
header to the drivers/dma/ directory and add the test driver there.
Arnd
next prev parent reply other threads:[~2014-10-21 9:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 12:00 [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support Srikanth Thokala
2014-10-15 12:45 ` Mark Rutland
2014-10-15 13:32 ` Vinod Koul
[not found] ` <20141015133248.GQ1638-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-15 15:00 ` Mark Rutland
2014-10-15 14:34 ` Srikanth Thokala
2014-10-20 19:37 ` Arnd Bergmann
2014-10-21 9:06 ` Appana Durga Kedareswara Rao
2014-10-21 9:14 ` Arnd Bergmann [this message]
2014-10-24 12:08 ` Appana Durga Kedareswara Rao
2014-10-24 13:58 ` Arnd Bergmann
2015-01-19 14:08 ` Appana Durga Kedareswara Rao
2015-01-29 11:24 ` Appana Durga Kedareswara Rao
2015-02-12 9:34 ` Vinod Koul
2015-02-14 14:21 ` Appana Durga Kedareswara Rao
[not found] ` <ed439c7a25d0465d9dbf4c06987d42a1-neA4ZlFjCT2qEU4nYqjAjmYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-02-20 6:29 ` Vinod Koul
2015-02-20 10:42 ` Michal Simek
[not found] ` <ad1002303e814d53866349674d22fc11-neA4ZlFjCT0GPAd83OwqBWYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-03-02 16:38 ` Vinod Koul
[not found] ` <54E70F97.30908@xilinx.com>
2015-03-02 9:04 ` Appana Durga Kedareswara Rao
2015-02-05 13:31 ` Appana Durga Kedareswara Rao
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=3236720.MHeqOodrCV@wuerfel \
--to=arnd@arndb.de \
--cc=anirudh@xilinx.com \
--cc=appana.durga.rao@xilinx.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sthokal@xilinx.com \
--cc=svemula@xilinx.com \
--cc=vinod.koul@intel.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 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).