From: Andy Gross <agross@codeaurora.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v6 1/2] dmaengine: qcom_bam_dma: Add device tree binding
Date: Fri, 21 Feb 2014 13:02:06 -0600 [thread overview]
Message-ID: <20140221190206.GC3102@qualcomm.com> (raw)
In-Reply-To: <20140221173647.GC28555@e106331-lin.cambridge.arm.com>
On Fri, Feb 21, 2014 at 05:36:47PM +0000, Mark Rutland wrote:
[snip]
> >
> > Yes only a single interrupt. I can remove the s.
>
> Please don't, the interrupts proeprty is standard and shouldn't change.
>
> I was only asking to ensure that all interrupts were described in the
> binding, which they are. :)
>
Responding to emails before coffee is bad.....
--
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-21 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:43 [Patch v6 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
2014-02-21 6:43 ` [Patch v6 1/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-02-21 9:26 ` Mark Rutland
2014-02-21 16:30 ` Andy Gross
2014-02-21 17:36 ` Mark Rutland
2014-02-21 19:02 ` Andy Gross [this message]
2014-02-21 6:43 ` [Patch v6 2/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-02-21 9:33 ` Mark Rutland
[not found] ` <20140221093352.GE7541-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2014-02-21 17:22 ` 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=20140221190206.GC3102@qualcomm.com \
--to=agross@codeaurora.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=mark.rutland@arm.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).