Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754428AbZI3MQs (ORCPT ); Wed, 30 Sep 2009 08:16:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754408AbZI3MQr (ORCPT ); Wed, 30 Sep 2009 08:16:47 -0400 Received: from mail.gmx.net ([213.165.64.20]:46422 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753186AbZI3MQo (ORCPT ); Wed, 30 Sep 2009 08:16:44 -0400 X-Authenticated: #20450766 X-Provags-ID: V01U2FsdGVkX1/+IXYbGon+ocgo29eduPQeF2Y5XvnayUJv6immvK uex3y7LdOurzy8 Date: Wed, 30 Sep 2009 14:16:56 +0200 (CEST) From: Guennadi Liakhovetski To: Pavel Machek cc: Russell King - ARM Linux , Linus Torvalds , kernel list , Eric Miao , linux-arm-kernel , Robert Jarzmik , Linux Media Mailing List , Mauro Carvalho Chehab , Paul Mundt , Magnus Damm Subject: Re: arm tree in broken state (was Re: What's inside the pxa tree for this merge window) In-Reply-To: <20090930120920.GH1412@ucw.cz> Message-ID: References: <1253256227.4407.7.camel@pc-matejk> <20090918074551.GA26058@n2100.arm.linux.org.uk> <20090921200923.GF30821@n2100.arm.linux.org.uk> <20090930120920.GH1412@ucw.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2413 Lines: 56 Hi Pavel On Wed, 30 Sep 2009, Pavel Machek wrote: > > > > I discarded them _because_ Eric handled them, which is what I said in the > > > > comments when I discarded them. > > > > > > Ok, I did do my best to get patches in the right order in the mainline, > > > but it all failed. AFAICS, v4l and sh are already in the mainline with a > > > _wrongly_ resolved mefge conflict, which, most likely, breaks the > > > sh_mobile_ceu_camera.c driver, and the three PXA platforms, patches for > > > which should have been applied before both those trees and still haven't > > > been applied are broken until the patches do get in and the later those > > > patches get applied the longer the interval with the broken for them > > > bisection is going to be. > > > > Meanwhile I have to consider that we have several bug fixes outstanding, > > and since I can't send Linus a pull request every day (max once a week) > > I have to be very careful about when I send stuff. > > > > So I only get _two_ opportunities during a merge window to send a pull > > request. > > Well, you should certainly try to keep your tree unbroken, but when > it breaks, fixing it asap should be a priority. I don't know where you > got the 'once a week' rule, but it seems stupid. > > > I'm going to wait until tomorrow before sending my final pull for this > > window, which is the penultimate day before the window closes. > > > > Don't blame me for these delays - it's not my choice to impose such > > delays. I'd really like to fix those broken platforms right now. I > > just can't do so without causing additional delays for other issues. > > Blame Linus for imposing the "max one pull a week" rule on me. > > Do you have maillist reference? Not even Linus should slow down > development like that. > > If Linus really insists on that, perhaps possible solution would be to > make subarch maintainers send pull requests for simple fixes directly > to Linus? Thanks for your concern, but the patches are long in mainline, no reason to worry any more. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- 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/