Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753607AbcKUKhO (ORCPT ); Mon, 21 Nov 2016 05:37:14 -0500 Received: from mga11.intel.com ([192.55.52.93]:48395 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753933AbcKUKhL (ORCPT ); Mon, 21 Nov 2016 05:37:11 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,674,1473145200"; d="scan'208";a="7341077" Message-ID: <1479724626.22212.50.camel@linux.intel.com> Subject: Re: [PATCH v3 0/2] DW DMAC: update device tree From: Andy Shevchenko To: Alexey Brodkin Cc: "vinod.koul@intel.com" , "linux-kernel@vger.kernel.org" , "robh+dt@kernel.org" , "devicetree@vger.kernel.org" , "Eugeniy.Paltsev@synopsys.com" , "linux-snps-arc@lists.infradead.org" , "mark.rutland@arm.com" , "dmaengine@vger.kernel.org" Date: Mon, 21 Nov 2016 12:37:06 +0200 In-Reply-To: <1479722477.2487.5.camel@synopsys.com> References: <1479496356-27834-1-git-send-email-Eugeniy.Paltsev@synopsys.com> <1479497189.22212.41.camel@linux.intel.com> <1479722477.2487.5.camel@synopsys.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.2-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1454 Lines: 36 On Mon, 2016-11-21 at 10:02 +0000, Alexey Brodkin wrote: > 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. I understand your concern, I'm often in the same position in many areas, including this driver (I'm not a maintainer of slave DMA subsystem). Though let's face the issues we have with the series: - stuff regarding to style and alike (would be fixed in a day) - DTS naming and conventions, this is apparently a big area, where I might share opinion, but can't decide for - last word by the subsystem maintainer > 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. Vinod, is it possible to get in for this series (if we get Ack from DT people)? -- Andy Shevchenko Intel Finland Oy