From: Vinod Koul <vinod.koul@intel.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
mark.rutland@arm.com, timur@codeaurora.org, cov@codeaurora.org,
jcm@redhat.com, agross@codeaurora.org, arnd@arndb.de,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
Date: Mon, 4 Jan 2016 09:06:58 +0530 [thread overview]
Message-ID: <20160104033658.GB2940@localhost> (raw)
In-Reply-To: <5689B833.7010901@codeaurora.org>
On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote:
> Hi Vinod,
>
> >
>
> Can I have your ACK on your series if you are OK?
Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on
DT patches first :)
--
~Vinod
next prev parent reply other threads:[~2016-01-04 3:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 0:06 [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 1/7] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 2/7] dma: hidma: Add Device Tree support Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 3/7] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2016-01-04 18:37 ` Andy Shevchenko
2016-01-05 4:46 ` Vinod Koul
2016-01-10 13:14 ` Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 4/7] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2016-01-04 18:43 ` Andy Shevchenko
2016-01-05 14:05 ` Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 5/7] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-01-04 19:01 ` Andy Shevchenko
2016-01-10 14:03 ` Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 6/7] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-01-04 0:06 ` [PATCH V11 7/7] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-01-04 0:09 ` [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-01-04 3:36 ` Vinod Koul [this message]
2016-01-04 3:51 ` Sinan Kaya
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=20160104033658.GB2940@localhost \
--to=vinod.koul@intel.com \
--cc=agross@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jcm@redhat.com \
--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=okaya@codeaurora.org \
--cc=timur@codeaurora.org \
/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