Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754152Ab3JDLue (ORCPT ); Fri, 4 Oct 2013 07:50:34 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40474 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753518Ab3JDLuc (ORCPT ); Fri, 4 Oct 2013 07:50:32 -0400 Date: Fri, 4 Oct 2013 12:50:22 +0100 From: Russell King - ARM Linux To: Olof Johansson Cc: Greg Kroah-Hartman , linux-arm-msm@vger.kernel.org, Feng Kan , Linux Kernel list , "linux-arm-kernel@lists.infradead.org" , Kumar Gala Subject: Re: Use of drivers/platform and matching include? Message-ID: <20131004115022.GN12758@n2100.arm.linux.org.uk> References: <20131003170914.GA11992@kroah.com> 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: 1422 Lines: 28 On Thu, Oct 03, 2013 at 10:54:07AM -0700, Olof Johansson wrote: > It wouldn't be a huge deal to add something like arch/arm/syslib and > give some of the system library-type code a home there -- stuff like > resource allocation libraries, etc. I don't think we want to collect > all the back-end drivers in there though, just libraries. We don't need yet another subdirectory in arch/arm - yes, that's a favourite way of avoiding any issues, but really it's not the right answer. We already have a place for shared cross-platform code, and it's called arch/arm/common. > I think many of us are hesitant to introduce something that runs the > risk of becoming a dumping ground for all these "I don't know where to > put them, so here you go" drivers, since we've spent so much time > cleaning them all up and de-forking per-vendor implementations of > similar things. "Drivers go under drivers/" is what we've decided. If we want to change that, then we should move all those IRQ, gpio and clock drivers back out of the drivers/ subtree, because many of them are SoC specific. Please, think back to why we made the original decision(s) to move this stuff out of arch/arm. -- 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/