Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753849Ab3JDLlr (ORCPT ); Fri, 4 Oct 2013 07:41:47 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40465 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751817Ab3JDLlq (ORCPT ); Fri, 4 Oct 2013 07:41:46 -0400 Date: Fri, 4 Oct 2013 12:41:28 +0100 From: Russell King - ARM Linux To: Olof Johansson Cc: Kumar Gala , Greg Kroah-Hartman , Linux Kernel list , "linux-arm-kernel@lists.infradead.org" , linux-arm-msm@vger.kernel.org Subject: Re: Use of drivers/platform and matching include? Message-ID: <20131004114128.GL12758@n2100.arm.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1398 Lines: 27 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. :( Are you seriously suggesting going back to having drivers under arch/arm because we can't find a home for them in the drivers subtree? Having made a big thing about things as small as clock source drivers, IRQ drivers and such like which "shouldn't be under arch/arm" and moving them out, to then say about finding somewhere under arch/arm for drivers is very much a case of double-standards. I've heard this accusation that we have too many drivers in arch/arm many times, and although we've made some progress getting things like clock and IRQ drivers out of arch/arm, we're still a long way from sorting that out. Or maybe that original accusation was baseless for modern kernels, based on the old 1.x days when we had a arch/arm/drivers subdirectory which people have a hard time forgetting? So, no, there will be no new drivers under arch/arm. They must be in the drivers subtree somewhere. -- 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/