From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 0/7] MIPS: Move device-tree files to a common location Date: Mon, 25 Aug 2014 10:12:10 +0200 Message-ID: <2336240.173zr5MfQE@wuerfel> References: <1408651466-8334-1-git-send-email-abrestic@chromium.org> <20140823161456.GA2758@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: Rob Herring Cc: Olof Johansson , Andrew Bresticker , Florian Fainelli , Kumar Gala , Ralf Baechle , David Daney , Rob Herring , Linux-MIPS , Qais Yousef , Ian Campbell , "linux-kernel@vger.kernel.org" , Pawel Moll , John Crispin , Mark Rutland , Jayachandran C , Paul Burton , James Hogan , "devicetree@vger.kernel.org" List-Id: devicetree@vger.kernel.org On Sunday 24 August 2014 18:43:35 Rob Herring wrote: > On Sat, Aug 23, 2014 at 11:14 AM, Olof Johansson wrote: > > On Sat, Aug 23, 2014 at 03:56:42PM +0200, Arnd Bergmann wrote: > >> > >> Another argument is that we plan to actually move all the dts files out of > >> the kernel into a separate project in the future. We really don't want to > >> have the churn of moving all the files now when they get deleted in one > >> of the next merge windows. > > > > To be honest, I don't see that happening within the forseeable > > future. Some of us maintainers like talking about this, but everyone who > > actually develops have nightmares about this scenario. Nobody knows how > > it'll be done without causing some real serious impact on productivity. > > > >> I don't know if we talked about whether that move should be done for > >> all architectures at the same time. If that is the plan, I think it > >> would be best to not move the MIPS files at all but also wait until > >> they can get removed from the kernel tree. > > > > If MIPS can restructure now before things start growing, then I'd really > > recommend that they do so and not hold off waiting on some event that > > might never happen. > > Yes, I agree on both points. > Ok, fair enough. Arnd