linux-kernel - Re: arm tree in broken state (was Re: What's inside the pxa tree for this merge window)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0909301415300.4330@axis700.grange>
Date:	Wed, 30 Sep 2009 14:16:56 +0200 (CEST)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Pavel Machek <pavel@....cz>
cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	kernel list <linux-kernel@...r.kernel.org>,
	Eric Miao <eric.y.miao@...il.com>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Robert Jarzmik <robert.jarzmik@...e.fr>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Paul Mundt <lethal@...ux-sh.org>,
	Magnus Damm <magnus.damm@...il.com>
Subject: Re: arm tree in broken state (was Re: What's inside the pxa tree
 for this merge window)

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/