linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.16-rc4
Date: Fri, 8 Aug 2014 21:49:52 -0500	[thread overview]
Message-ID: <20140809024952.GA31064@saruman.home> (raw)
In-Reply-To: <alpine.DEB.2.02.1408082338380.30868@utopia.booyaka.com>

Hi,

On Fri, Aug 08, 2014 at 11:39:08PM +0000, Paul Walmsley wrote:
> On Fri, 8 Aug 2014, Felipe Balbi wrote:
> 
> > On Fri, Aug 08, 2014 at 06:11:54AM +0000, Paul Walmsley wrote:
> > > On Thu, 7 Aug 2014, Felipe Balbi wrote:
> > > 
> > > > we have stable releases for that.
> > > 
> > > Stable releases aren't a fix for process failures.
> > 
> > of course not, but your claim that there's no way to fix v3.16 is
> > nonsense. And mistakes occur as well.
> 
> There is no way to fix v3.16. 

There is no way to fix *any* commit.

We can go back a few major releases and we will hit a point when ARM
multiplatform was enabled and the tree doesn't even build. There is no
way to fix that either, but I'm sure the patches fixing the build breaks
have been back ported to stable.

> The point of the -rc cycle is to stabilize the final, non-rc releases.

Well, stable release are *not* -rc releases and they exist in order to
fix bugs that were found after the final release has been tagged;
otherwise what would be the point of even having -stable ?

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140808/7197b5e8/attachment.sig>

  reply	other threads:[~2014-08-09  2:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06 23:41 OMAP baseline test results for v3.16-rc4 Paul Walmsley
2014-07-07  8:02 ` Tony Lindgren
2014-07-14 17:28   ` Paul Walmsley
2014-07-15  6:04     ` Tony Lindgren
2014-07-15 19:56       ` Paul Walmsley
2014-07-25 19:14   ` Paul Walmsley
2014-07-29  6:42     ` Tony Lindgren
2014-07-29  8:25       ` Paul Walmsley
2014-07-29  8:49         ` Tony Lindgren
2014-07-29 12:32           ` Paul Walmsley
2014-07-29 12:57             ` Paul Walmsley
2014-07-29 14:53               ` Tony Lindgren
2014-07-29 19:37                 ` Paul Walmsley
2014-07-30  5:39                   ` Tony Lindgren
2014-07-30  7:53                     ` Paul Walmsley
2014-07-31 13:11                       ` Tony Lindgren
2014-07-31 19:27                         ` Paul Walmsley
2014-08-01  7:10                           ` Tony Lindgren
2014-08-01  7:52                             ` Tony Lindgren
2014-08-07 22:21                             ` Paul Walmsley
2014-08-08  2:14                               ` Felipe Balbi
2014-08-08  6:11                                 ` Paul Walmsley
2014-08-08 14:34                                   ` Felipe Balbi
2014-08-08 23:39                                     ` Paul Walmsley
2014-08-09  2:49                                       ` Felipe Balbi [this message]
2014-08-08  2:29                               ` Fabio Estevam
2014-08-08  6:14                                 ` Paul Walmsley
2014-08-09 12:41                               ` Ezequiel Garcia
2014-07-31 13:12                     ` Tero Kristo
2014-07-29  8:50         ` Paul Walmsley

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=20140809024952.GA31064@saruman.home \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).