From: Mark Rutland <mark.rutland@arm.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: robh+dt@kernel.org, frowand.list@gmail.com,
grant.likely@linaro.org, devicetree@vger.kernel.org,
dmaengine@vger.kernel.org, timur@codeaurora.org,
cov@codeaurora.org, vinod.koul@intel.com, jcm@redhat.com,
arnd@arndb.de, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, agross@codeaurora.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V9 2/5] dma: add Qualcomm Technologies HIDMA management driver
Date: Wed, 13 Jan 2016 19:02:20 +0000 [thread overview]
Message-ID: <20160113190220.GO23370@leverpostej> (raw)
In-Reply-To: <5696907C.6000809@codeaurora.org>
On Wed, Jan 13, 2016 at 12:59:24PM -0500, Sinan Kaya wrote:
> Hi Mark, Rob, Frank, Grant and other DT experts;
> I have been trying to reach to device tree reviewers without any luck for the last two weeks.
> It must be the holidays.
Indeed. Apologies for the delay.
> I have restructured the code address concerns from Mark Rutland above. The dma-engine maintainer, Vinod Koul;
> is looking for an ACK from the DT community before the patches can be incorporated.
>
> Could you please kindly review the series here from DT perspective and ACK it if you are OK?
> https://lkml.org/lkml/2016/1/11/517
I will try to look at v12 shortly (i.e. in the next day or two).
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V9 2/5] dma: add Qualcomm Technologies HIDMA management driver
Date: Wed, 13 Jan 2016 19:02:20 +0000 [thread overview]
Message-ID: <20160113190220.GO23370@leverpostej> (raw)
In-Reply-To: <5696907C.6000809@codeaurora.org>
On Wed, Jan 13, 2016 at 12:59:24PM -0500, Sinan Kaya wrote:
> Hi Mark, Rob, Frank, Grant and other DT experts;
> I have been trying to reach to device tree reviewers without any luck for the last two weeks.
> It must be the holidays.
Indeed. Apologies for the delay.
> I have restructured the code address concerns from Mark Rutland above. The dma-engine maintainer, Vinod Koul;
> is looking for an ACK from the DT community before the patches can be incorporated.
>
> Could you please kindly review the series here from DT perspective and ACK it if you are OK?
> https://lkml.org/lkml/2016/1/11/517
I will try to look at v12 shortly (i.e. in the next day or two).
Thanks,
Mark.
next prev parent reply other threads:[~2016-01-13 19:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 16:16 [PATCH V9 0/5] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2015-12-11 16:16 ` Sinan Kaya
2015-12-11 16:16 ` [PATCH V9 1/5] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2015-12-11 16:16 ` Sinan Kaya
2015-12-11 16:16 ` [PATCH V9 2/5] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2015-12-11 16:16 ` Sinan Kaya
2015-12-11 16:41 ` Mark Rutland
2015-12-11 16:41 ` Mark Rutland
2015-12-11 19:09 ` Sinan Kaya
2015-12-11 19:09 ` Sinan Kaya
2015-12-11 19:37 ` Mark Rutland
2015-12-11 19:37 ` Mark Rutland
2015-12-11 22:14 ` Sinan Kaya
2015-12-11 22:14 ` Sinan Kaya
2015-12-14 12:05 ` Mark Rutland
2015-12-14 12:05 ` Mark Rutland
2015-12-15 5:43 ` Sinan Kaya
2015-12-15 5:43 ` Sinan Kaya
2016-01-10 14:08 ` Sinan Kaya
2016-01-10 14:08 ` Sinan Kaya
[not found] ` <569265D6.5060407-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-13 17:59 ` Sinan Kaya
2016-01-13 17:59 ` Sinan Kaya
2016-01-13 17:59 ` Sinan Kaya
2016-01-13 19:02 ` Mark Rutland [this message]
2016-01-13 19:02 ` Mark Rutland
2015-12-11 16:16 ` [PATCH V9 3/5] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2015-12-11 16:16 ` Sinan Kaya
2015-12-11 16:17 ` [PATCH V9 4/5] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2015-12-11 16:17 ` Sinan Kaya
2015-12-11 16:17 ` [PATCH V9 5/5] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2015-12-11 16:17 ` 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=20160113190220.GO23370@leverpostej \
--to=mark.rutland@arm.com \
--cc=agross@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.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=okaya@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=timur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.