Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932201AbZFLBZn (ORCPT ); Thu, 11 Jun 2009 21:25:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754038AbZFLBZc (ORCPT ); Thu, 11 Jun 2009 21:25:32 -0400 Received: from 130.120.124.202.static.snap.net.nz ([202.124.120.130]:39729 "EHLO hayes.bluewaternz.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754010AbZFLBZc (ORCPT ); Thu, 11 Jun 2009 21:25:32 -0400 Message-ID: <4A31AECA.6070303@bluewatersys.com> Date: Fri, 12 Jun 2009 13:26:34 +1200 From: Ryan Mallon User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Nicolas Pitre CC: Russell King - ARM Linux , Tony Lindgren , Alan Cox , David Miller , swetland@google.com, pavel@ucw.cz, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk, san@android.com, rlove@google.com Subject: Re: HTC Dream aka. t-mobile g1 support References: <20090611111821.GK795@n2100.arm.linux.org.uk> <20090611.042226.28424489.davem@davemloft.net> <20090611114911.GL795@n2100.arm.linux.org.uk> <20090611.050030.169859977.davem@davemloft.net> <20090611123852.GM795@n2100.arm.linux.org.uk> <20090611135442.6b9ab315@lxorguk.ukuu.org.uk> <20090611132134.GA11199@atomide.com> <20090611133736.GP795@n2100.arm.linux.org.uk> <20090611140038.GB11199@atomide.com> <20090611140624.GS795@n2100.arm.linux.org.uk> <4A3175AC.9070100@bluewatersys.com> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2986 Lines: 60 Nicolas Pitre wrote: > On Fri, 12 Jun 2009, Ryan Mallon wrote: > >> Nicolas Pitre wrote: >>> On Thu, 11 Jun 2009, Russell King - ARM Linux wrote: >>> >>> I think that you, as the ARM maintainer, should continue gathering all >>> the ARM subarchitectures into a coherent ARM tree and arbitrate >>> conflicts when they occur. You should especially keep a tight control >>> on the very core ARM code. But everything under arch/arm/mach-* you >>> should let people maintaining those have control of that themselves and >>> free yourself from that responsibility as much as possible. The current >>> directory structure is quite indicative of where the boundaries are >>> already. This way, if I make a mess of arch/arm/mach-orion5x/* then you >>> just need to pass the blame straight to me. >>> >> That works okay for the more popular sub-architectures like pxa, etc, >> where there are a lot of people to review code and sort out issues >> between themselves. However, for the architecture I do most of my work >> on, ep93xx, there are basically two of us, Hartley and myself, doing >> active work. >> >> It seems a bit dodgy if all the patches to ep93xx are written by one of >> us and acked by the other with no input from anybody else. It would be >> very easy for the ep93xx code to become and complete mess, and lack any >> coherency with the other sub-archs. I prefer having Russell, or somebody >> else, at least have a glance at the patches before they get applied. > > This is all fine. If you prefer some external help to judge your > patches that's OK. In fact I'm not advocating for people to stop > posting their patches to linux-arm-kernel at all. It is a good thing > for patches to be aired on the mailing list for everyone to see and > comment. > > However if you start gathering more developers around the ep93xx then > someone should take charge and be responsible for it. And this must not > necessarily be Russell as his cycles are not infinite. Thats my point though: In the meantime, it falls on Russell by default to be the one to verify all the patches going through. I think the same is true for new architectures, if nobody else has the interest/hardware besides those posting the patches, then who is meant to do the reviewing/acking? ~Ryan -- Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon Unit 5, Amuri Park Phone: +64 3 3779127 404 Barbadoes St Fax: +64 3 3779135 PO Box 13 889 Email: ryan@bluewatersys.com Christchurch, 8013 Web: http://www.bluewatersys.com New Zealand Freecall Australia 1800 148 751 USA 1800 261 2934 -- 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/