[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090611165147.0769adfb@lxorguk.ukuu.org.uk>
Date: Thu, 11 Jun 2009 16:51:47 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Tony Lindgren <tony@...mide.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
David Miller <davem@...emloft.net>, swetland@...gle.com,
pavel@....cz, 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
> - I wait few days and if no comments, pile them into for-next
>
> - I send a pull request to you to keep things coordinated for arm
You don't even need that - you can decouple that further and there are
good reasons to do so to some extent.
> - If you want something merged earlier, you let know and send pull
> request
>
> I'm flexible, and willing to try other things if that helps you.
> But I think we (as arm community) should coordinate the arm patches
> ourselves. So I'd rather see you pull in stuff and send it to
> Linus rather than bug Linus with a pull request for stuff that
> he may not care too much about.
The sooner its in next the sooner its really visible. Whether Russell
pulls your tree for the final merge and resends it on or you do it
directly is fairly irrelevant to the final merge but you maximise
exposure if linux-next is directly pulling your trees and adding them
after the arm tree somewhere. If you get collisions Stephen will just
drop your tree while you fix it. Similarly if you end up with an overlap
where your patches end up in both trees git will figure it out itself.
Alan
--
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