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:58:13 -0700 [thread overview]
Message-ID: <20100427165813.GC7225@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004270934220.3739@i5.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> [100427 09:31]:
>
>
> On Tue, 27 Apr 2010, Tony Lindgren wrote:
> >
> > OK point taken. I should have dealt with this earlier. Will only queue
> > regressions after -rc3 or so.
>
> Note that the "only regressions" is certainly not a hard rule. Anything
> that would be valid for -stable is obviously always valid: security
> issues, major oopses etc etc.
Sure.
> But the "only regressions" should kind of be the guiding line, and the
> others are more like "this is so serious that it should go in regardless
> of anything else".
OK. I guess was using criteria like "this is needed to boot this and that
board in a usable way" and "let's get all the fixes in" criteria, but that
should have been done way earlier.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v2.6.34-rc5
Date: Tue, 27 Apr 2010 09:58:13 -0700 [thread overview]
Message-ID: <20100427165813.GC7225@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004270934220.3739@i5.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> [100427 09:31]:
>
>
> On Tue, 27 Apr 2010, Tony Lindgren wrote:
> >
> > OK point taken. I should have dealt with this earlier. Will only queue
> > regressions after -rc3 or so.
>
> Note that the "only regressions" is certainly not a hard rule. Anything
> that would be valid for -stable is obviously always valid: security
> issues, major oopses etc etc.
Sure.
> But the "only regressions" should kind of be the guiding line, and the
> others are more like "this is so serious that it should go in regardless
> of anything else".
OK. I guess was using criteria like "this is needed to boot this and that
board in a usable way" and "let's get all the fixes in" criteria, but that
should have been done way earlier.
Regards,
Tony
next prev parent reply other threads:[~2010-04-27 16:58 UTC|newest]
Thread overview: 11+ 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-26 19:00 ` Tony Lindgren
2010-04-27 15:31 ` Linus Torvalds
2010-04-27 15:31 ` Linus Torvalds
2010-04-27 15:31 ` Linus Torvalds
2010-04-27 16:12 ` Tony Lindgren
2010-04-27 16:12 ` Tony Lindgren
2010-04-27 16:35 ` Linus Torvalds
2010-04-27 16:35 ` Linus Torvalds
2010-04-27 16:58 ` Tony Lindgren [this message]
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=20100427165813.GC7225@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.