From: okaya@codeaurora.org
To: Vinod Koul <vinod.koul@intel.com>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
devicetree@vger.kernel.org, cov@codeaurora.org, jcm@redhat.com,
shankerd@codeaurora.org, vikrams@codeaurora.org,
marc.zyngier@arm.com, mark.rutland@arm.com,
eric.auger@linaro.org, agross@codeaurora.org, arnd@arndb.de,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver
Date: Sun, 20 Mar 2016 09:30:50 -0400 [thread overview]
Message-ID: <115f141fa85206e54783964bcd25be32@codeaurora.org> (raw)
In-Reply-To: <20160320093926.GM2490@localhost>
On 2016-03-20 05:39, Vinod Koul wrote:
> On Fri, Mar 11, 2016 at 04:49:50PM -0500, Sinan Kaya wrote:
>>
>> Sinan Kaya (4):
>> dma: qcom_hidma: implement lower level hardware interface
>> dma: qcom_hidma: add debugfs hooks
>> dma: qcom_hidma: add support for object hierarchy
>> dma: qcom_hidma: read the channel id from HW
>
> Any reason why you insist on using subsystem name as dma even when
> asked to
> change..
Forgotten. I can fix that.
next prev parent reply other threads:[~2016-03-20 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 21:49 [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 1/4] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 2/4] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 3/4] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-03-11 21:49 ` [PATCH 4/4] dma: qcom_hidma: read the channel id from HW Sinan Kaya
2016-03-18 20:06 ` Rob Herring
[not found] ` <1457732994-11175-1-git-send-email-okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-03-20 9:39 ` [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver Vinod Koul
2016-03-20 13:30 ` okaya [this message]
2016-03-27 13:11 ` okaya-sgV2jX0FEOL9JmXXK+q4OQ
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=115f141fa85206e54783964bcd25be32@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=eric.auger@linaro.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=shankerd@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=vikrams@codeaurora.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).