public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] omap fixes for v2.6.34-rc5
Date: Tue, 27 Apr 2010 09:12:17 -0700	[thread overview]
Message-ID: <20100427161217.GB7225@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004270831430.3739@i5.linux-foundation.org>

* Linus Torvalds <torvalds@linux-foundation.org> [100427 08:28]:
> 
> On Mon, 26 Apr 2010, Tony Lindgren wrote:
> > 
> > Please pull omap fixes from:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-fixes-for-linus
> 
> I pulled it this time, but I'm starting to get really irritated with you.
> 
> These look like real fixes, but quite frankly, by -rc5, that IS NOT 
> ENOUGH. 
> 
> They need to be _regressions_, not just cleanups and fixes for things that 
> have never worked. And this is starting to be a pattern with the omap 
> tree: you're not honoring the merge window properly.
> 
> Just "it's a bug-fix" or "it's deleting unused code" is not enough. The 
> point of the late -rc series is to fix problems from the merge window, not 
> add new changes. I realize that you think that all the new changes are 
> obviously good, but the fact is, bugs happen even in "obvious bug-fixes". 
> 
> And that's why we have the rule about late-rc pulls being about 
> _regressions_ and/or major oopses/security issues. Not just random 
> development that are meant to improve things.

OK point taken. I should have dealt with this earlier. Will only queue
regressions after -rc3 or so.

Regards,

Tony

  reply	other threads:[~2010-04-27 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 19:00 [GIT PULL] omap fixes for v2.6.34-rc5 Tony Lindgren
2010-04-27 15:31 ` Linus Torvalds
2010-04-27 16:12   ` Tony Lindgren [this message]
2010-04-27 16:35     ` Linus Torvalds
2010-04-27 16:58       ` Tony Lindgren

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=20100427161217.GB7225@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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