From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755006AbcBIDRa (ORCPT ); Mon, 8 Feb 2016 22:17:30 -0500 Received: from mga03.intel.com ([134.134.136.65]:59419 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751870AbcBIDR1 (ORCPT ); Mon, 8 Feb 2016 22:17:27 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,418,1449561600"; d="scan'208";a="911285889" Date: Tue, 9 Feb 2016 08:51:05 +0530 From: Vinod Koul To: Heiko Stuebner , g@mail.home.local Cc: Caesar Wang , Caesar Wang , Mark Rutland , devicetree@vger.kernel.org, Russell King , Pawel Moll , Ian Campbell , linux-kernel@vger.kernel.org, shawn.lin@rock-chips.com, dianders@chromium.org, Rob Herring , linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org, Mark Brown , Kumar Gala , dmaengine@vger.kernel.org, Dan Williams , Sonny Rao , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Message-ID: <20160209032105.GD19598@localhost> References: <1453460812-8498-1-git-send-email-wxt@rock-chips.com> <3817335.PXCk0JfYDT@phil> <20160208131419.GA19598@localhost> <2223201.4nEkyUQu1O@phil> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2223201.4nEkyUQu1O@phil> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 08, 2016 at 11:21:57PM +0100, Heiko Stuebner wrote: > Hi Vinod, > > Am Montag, 8. Februar 2016, 18:44:19 schrieb Vinod Koul: > > On Mon, Feb 08, 2016 at 10:27:04AM +0100, Heiko Stuebner wrote: > > > Am Montag, 8. Februar 2016, 08:41:34 schrieb Vinod Koul: > > > > On Mon, Feb 01, 2016 at 02:56:54PM +0800, Caesar Wang wrote: > > > > > Hello Vinod, > > > > > > > > > > Is there any chance apply the DMA patches?:-) > > > > > > > > I was waiting for any ACKs on ARM patches before I merge this series. > > > > > > I think the more regular way is for the driver maintainer to take the > > > driver-specific stuff and the devicetree parts going through the > > > specific arm- tree. But if you really want to take the whole series, > > > for patches 4,5,6 > > Yes but that causes cross tree dependencies, which looking at this won't > > be a big problem, so I can safely merge dmaengine changes and rest can go > > thru ARM tree. > > > > Typically submitter should say which tree he/she prefers, which was not > > provided.. > > > > So, are all okay to merge the entire series thru dmaengine tree or > > independent. I don't mind either > > In general I don't mind either solution, but would prefer me taking the 3 > "ARM: dts: foo" patches, while the rest would go through your tree. > > Main reason is to prevent any possible conflicts with other Rockchip > devicetree additions also going into 4.6 . Sounds good, will queue them up -- ~Vinod