From mboxrd@z Thu Jan 1 00:00:00 1970 From: balbi@ti.com (Felipe Balbi) Date: Fri, 8 Aug 2014 21:49:52 -0500 Subject: OMAP baseline test results for v3.16-rc4 In-Reply-To: References: <20140730053940.GX29045@atomide.com> <20140731131107.GB29045@atomide.com> <20140801071056.GD29045@atomide.com> <20140808021442.GA22811@saruman.home> <20140808143411.GA2288@saruman.home> Message-ID: <20140809024952.GA31064@saruman.home> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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: