From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: Use of drivers/platform and matching include? Date: Fri, 4 Oct 2013 12:43:40 +0100 Message-ID: <20131004114340.GM12758@n2100.arm.linux.org.uk> References: <20131003170914.GA11992@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40469 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754045Ab3JDLnt (ORCPT ); Fri, 4 Oct 2013 07:43:49 -0400 Content-Disposition: inline In-Reply-To: <20131003170914.GA11992@kroah.com> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Greg Kroah-Hartman Cc: Olof Johansson , linux-arm-msm@vger.kernel.org, Linux Kernel list , "linux-arm-kernel@lists.infradead.org" , Kumar Gala On Thu, Oct 03, 2013 at 10:09:14AM -0700, Greg Kroah-Hartman wrote: > On Thu, Oct 03, 2013 at 09:46:30AM -0700, Olof Johansson wrote: > > I don't have a good answer though. If it wasn't for the arm64 fork, > > locating these under arch/arm somewhere would really be the reasonable > > answer, like we used to do on powerpc. :( > > Sounds like yet-another-good reason why there shouldn't be an arm64 > "fork" at all :( > > The arm community created this mess, you all can fix it up, it's not too > late. I said at the time, way before arm64 was merged that it should not be a separate arch. Every bit of feedback I gave on arm64 got shouted down by Catalin. ARM64 is Catalin's baby and he wants to protect it at all costs. I'm surprised Linus even pulled it in with no argument.