From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "vinod.koul@intel.com" <vinod.koul@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] DW DMAC: update device tree
Date: Mon, 21 Nov 2016 10:02:14 +0000 [thread overview]
Message-ID: <1479722477.2487.5.camel@synopsys.com> (raw)
In-Reply-To: <1479497189.22212.41.camel@linux.intel.com>
Hi Andy,
On Fri, 2016-11-18 at 21:26 +0200, Andy Shevchenko wrote:
> On Fri, 2016-11-18 at 22:12 +0300, Eugeniy Paltsev wrote:
> >
> > It wasn't possible to enable some features like
> > memory-to-memory transfers or multi block transfers via DT.
> > It is fixed by these patches.
>
> First of all, please, give time to reviewers to comment the patches.
> Usually it should be at least 24h (for the series that has been sent
> first time 1 week approximately).
I'm not really sure a lot of people get disturbed by this series
and given this all has been discussed for months now I'd really like
to see changes required for our HW to work to land in upstream ASAP.
Too bad we're late for 4.9 (which is supposed to be the next LTS) but
we need to make sure this series hits 4.10 for sure.
Hope this race doesn't affect you that much.
-Alexey
next prev parent reply other threads:[~2016-11-21 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 19:12 [PATCH v3 0/2] DW DMAC: update device tree Eugeniy Paltsev
2016-11-18 19:12 ` [PATCH v3 1/2] DW DMAC: enable memory-to-memory transfers support Eugeniy Paltsev
[not found] ` <1479496356-27834-2-git-send-email-Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-11-18 19:27 ` Andy Shevchenko
2016-11-18 19:12 ` [PATCH v3 2/2] DW DMAC: add multi-block property to device tree Eugeniy Paltsev
[not found] ` <1479496356-27834-3-git-send-email-Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-11-18 19:33 ` Andy Shevchenko
2016-11-23 4:15 ` Vinod Koul
2016-11-21 13:53 ` Arnd Bergmann
[not found] ` <1479496356-27834-1-git-send-email-Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-11-18 19:26 ` [PATCH v3 0/2] DW DMAC: update " Andy Shevchenko
2016-11-21 10:02 ` Alexey Brodkin [this message]
[not found] ` <1479722477.2487.5.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-11-21 10:37 ` Andy Shevchenko
[not found] ` <1479724626.22212.50.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-11-23 4:06 ` Vinod Koul
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=1479722477.2487.5.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).