From: Felipe Balbi <balbi@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Felipe Balbi <balbi@ti.com>, Andy Gross <agross@codeaurora.org>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch v7 2/2] dmaengine: add Qualcomm BAM dma driver
Date: Mon, 24 Feb 2014 23:00:53 -0600 [thread overview]
Message-ID: <20140225050053.GA15411@saruman.home> (raw)
In-Reply-To: <20140225030459.GN25940@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 408 bytes --]
On Tue, Feb 25, 2014 at 12:05:00PM +0900, Mark Brown wrote:
> On Mon, Feb 24, 2014 at 06:09:13PM -0600, Felipe Balbi wrote:
>
> > > + depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
>
> > do you really want to make it depend on ARM even when COMPILE_TEST=y ?
>
> writel_relaxed() is unfortunately not generally available so it'd fail
> to build on platforms like x86.
bummer
--
balbi
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-02-25 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 23:11 [Patch v7 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
[not found] ` <1393283500-18599-1-git-send-email-agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-02-24 23:11 ` [Patch v7 1/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-02-24 23:11 ` [Patch v7 2/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-02-25 0:09 ` Felipe Balbi
2014-02-25 3:05 ` Mark Brown
2014-02-25 5:00 ` Felipe Balbi [this message]
2014-02-26 16:51 ` Stanimir Varbanov
2014-02-26 17:06 ` Andy Gross
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=20140225050053.GA15411@saruman.home \
--to=balbi@ti.com \
--cc=agross@codeaurora.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).