mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Paul Mundt <lethal@linux-sh.org>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: arm tree in broken state (was Re: What's inside the pxa tree for this merge window)
Date: Wed, 30 Sep 2009 14:16:56 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0909301415300.4330@axis700.grange> (raw)
In-Reply-To: <20090930120920.GH1412@ucw.cz>

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/

      reply	other threads:[~2009-09-30 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f17812d70909100446h17a1903fy74941945dbfc6943@mail.gmail.com>
     [not found] ` <1253256227.4407.7.camel@pc-matejk>
     [not found]   ` <20090918074551.GA26058@n2100.arm.linux.org.uk>
2009-09-21 19:19     ` What's inside the pxa tree for this merge window Guennadi Liakhovetski
2009-09-21 20:09       ` Russell King - ARM Linux
2009-09-21 20:32         ` Jamie Lokier
2009-09-30 12:09         ` arm tree in broken state (was Re: What's inside the pxa tree for this merge window) Pavel Machek
2009-09-30 12:16           ` Guennadi Liakhovetski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0909301415300.4330@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=eric.y.miao@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mchehab@infradead.org \
    --cc=pavel@ucw.cz \
    --cc=robert.jarzmik@free.fr \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®