Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759988Ab3ECMDC (ORCPT ); Fri, 3 May 2013 08:03:02 -0400 Received: from mail-ia0-f177.google.com ([209.85.210.177]:62459 "EHLO mail-ia0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753663Ab3ECMDA (ORCPT ); Fri, 3 May 2013 08:03:00 -0400 MIME-Version: 1.0 In-Reply-To: <20130503115739.GJ24153@gmail.com> References: <1367336497-10650-1-git-send-email-lee.jones@linaro.org> <20130501095243.GD25256@gmail.com> <20130503115739.GJ24153@gmail.com> Date: Fri, 3 May 2013 14:02:59 +0200 Message-ID: Subject: Re: [PATCH 1/5 v2] dmaengine: ste_dma40: Allow memcpy channels to be configured from DT From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Linus WALLEIJ , Srinidhi KASAGAR , Vinod Koul , Dan Williams , Per Forlin , Rabin Vincent Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2000 Lines: 50 On Fri, May 3, 2013 at 1:57 PM, Lee Jones wrote: > On Fri, 03 May 2013, Linus Walleij wrote: > >> On Wed, May 1, 2013 at 11:52 AM, Lee Jones wrote: >> >> > At this moment in time the memcpy channels which can be used by the D40 >> > are fixed, as each supported platform in Mainline uses the same ones. >> > However, platforms do exist which don't follow this convention, so >> > these will need to be tailored. Fortunately, these platforms will be DT >> > only, so this change has very little impact on platform data. >> > >> > Cc: Vinod Koul >> > Cc: Dan Williams >> > Cc: Per Forlin >> > Cc: Rabin Vincent >> > Signed-off-by: Lee Jones >> >> Real nice! >> >> But can you split this in two patches: one that changes >> drivers/dma/ste_dma40* and one sequel patch that changes >> Documentation/* and arch/arm/boot/dts/* so I can merge them >> out-of-order? >> >> I am trying this development cycle to split changes to the >> device trees and bindings off from the rest of the patches >> becaused it caused me a mess last cycle. > > I was under the impression that the documentation went with the > bindings, rather than the Device Tree. Am I wrong? No you're right. The documentation with the bindings and the patch to the driver... Then just arch/arm/boot/dts/* separately. The latter is where I have all my trouble and screwup... (However when we break the devicetree data out of the kernel and into its own git we will have to follow the pattern above with a patch of bindings+DT changes and another one in parallell changing the kernel, but that is for a more advanced age.) Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/