[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.0906111249110.31536@xanadu.home>
Date: Thu, 11 Jun 2009 12:57:19 -0400 (EDT)
From: Nicolas Pitre <nico@....org>
To: Kevin Hilman <khilman@...prootsystems.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
David Miller <davem@...emloft.net>, swetland@...gle.com,
pavel@....cz, lkml <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support
On Thu, 11 Jun 2009, Kevin Hilman wrote:
> Russell King - ARM Linux <linux@....linux.org.uk> writes:
>
> > On Thu, Jun 11, 2009 at 01:54:42PM +0100, Alan Cox wrote:
> >> Make your tree the core ARM code only, any other patches you don't
> >> accept. Aggressively push stuff out to platform code, and if people want
> >> to change core code "because our platform is different" make them extract
> >> it into the platform layer not carry it in the core bits.
> >
> > I'm all for giving this a try after this merge window is over.
>
> Speaking as maintainer of one ARM subarch (davinci) and active
> contributor to another (OMAP), I would gladly give this a try as well.
Speaking as maintainer of a couple other ARM subarchs (Orion, Kirkwood,
MV78xx0, ...) I would gladly accept full responsibility (and blame) for
them as well. I think Russell could avoid astraining to himself full
review for every patch concerning those that I send his way, and merely
look at the diffstat to be sure I'm not crapping onto the core ARM code.
Linus certainly doesn't do much more than that on his end already.
It's been a couple merge windows now that RMK started accepting git pull
requests from a couple people in addition to his patch system, and that
has worked pretty well overall.
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists