From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752912Ab1IUQWb (ORCPT ); Wed, 21 Sep 2011 12:22:31 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:51200 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752664Ab1IUQW3 (ORCPT ); Wed, 21 Sep 2011 12:22:29 -0400 From: Arnd Bergmann To: Linus Walleij Subject: Re: [PATCH 00/10] hwspinlock-next Date: Wed, 21 Sep 2011 18:21:54 +0200 User-Agent: KMail/1.12.2 (Linux/2.6.35-22-generic; KDE/4.3.2; x86_64; ; ) Cc: "Ohad Ben-Cohen" , Tony Lindgren , Andrew Morton , Greg KH , Russell King , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linus Torvalds , Nicolas Pitre , Thomas Gleixner , Stephen Rothwell , Grant Likely References: <1315846025-11453-1-git-send-email-ohad@wizery.com> <201109211612.33504.arnd@arndb.de> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109211821.55058.arnd@arndb.de> X-Provags-ID: V02:K0:16NYeQQeGGLIx4mEzYtOCvtRjOo5nRC6WYjXcPEJCvY epASPUqrZ12gQhcddBac7lZWXnFQb+pdfp/s/jMiQpp/z5dMKe O7jLh0zkvaso74l0+WgeysetNPAGAq+bOh07Ih6qLNPE3DJ8vN cdlpnViFPmoifQyOLqu91oL+e7/IcF8xx4TIk1vOEFAANcVkf7 4jZ06Pf5CryGbysi6UXXvpNJU8wxvG9UDlm4J/Z+/rOUWdf65C 4xr+vUH1dQn75ZZUzdGdwRzg/jNh4DyTHkRiVMaVMY8ikhOHJO B1sC7alx1R3GzqEh9fpmO7YCQ1bZN9Iv4TA5XBCcmUenljcrSe EivzvIPdwqWlo0KdR9Pw= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 21 September 2011, Linus Walleij wrote: > On Wed, Sep 21, 2011 at 4:12 PM, Arnd Bergmann wrote: > > > My feeling is that it would be best for Ohad to send these directly > > to Linus, since it's basically a standalone subsystem and he's listed > > as the maintainer (well, after this series at least). > > I agree. That's the path of least resistance and trouble. > > If/when ARM-specific driver subsystems need their own zuper-maintainer > we can deal with it, can't we? There aren't many of them yet. Definitely, I think that's the ideal case. I would very much like to see independent subsystem maintainers for the device drivers that are currently buried in per-architecture or per-platform directories. Among the ones that we should be moving out of there (or have already) are cpufreq, gpio, irqchip, pinmux, clock, dmaengine, timer, and there are probably some more. Since none of these are strictly ARM specific, my feeling is that they should not be part of the arm or arm-soc tree in the future but have their own trees. Arnd