From: Paul Walmsley <paul@pwsan.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v3.16-rc4
Date: Fri, 8 Aug 2014 23:39:08 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1408082338380.30868@utopia.booyaka.com> (raw)
In-Reply-To: <20140808143411.GA2288@saruman.home>
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.
The point of the -rc cycle is to stabilize the final, non-rc releases.
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.16-rc4
Date: Fri, 8 Aug 2014 23:39:08 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1408082338380.30868@utopia.booyaka.com> (raw)
In-Reply-To: <20140808143411.GA2288@saruman.home>
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.
The point of the -rc cycle is to stabilize the final, non-rc releases.
- Paul
next prev parent reply other threads:[~2014-08-08 23:39 UTC|newest]
Thread overview: 60+ 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-06 23:41 ` Paul Walmsley
2014-07-07 8:02 ` Tony Lindgren
2014-07-07 8:02 ` Tony Lindgren
2014-07-14 17:28 ` Paul Walmsley
2014-07-14 17:28 ` Paul Walmsley
2014-07-15 6:04 ` Tony Lindgren
2014-07-15 6:04 ` Tony Lindgren
2014-07-15 19:56 ` Paul Walmsley
2014-07-15 19:56 ` Paul Walmsley
2014-07-25 19:14 ` Paul Walmsley
2014-07-25 19:14 ` Paul Walmsley
2014-07-29 6:42 ` Tony Lindgren
2014-07-29 6:42 ` Tony Lindgren
2014-07-29 8:25 ` Paul Walmsley
2014-07-29 8:25 ` Paul Walmsley
2014-07-29 8:49 ` Tony Lindgren
2014-07-29 8:49 ` Tony Lindgren
2014-07-29 12:32 ` Paul Walmsley
2014-07-29 12:32 ` Paul Walmsley
2014-07-29 12:57 ` Paul Walmsley
2014-07-29 12:57 ` Paul Walmsley
2014-07-29 14:53 ` Tony Lindgren
2014-07-29 14:53 ` Tony Lindgren
2014-07-29 19:37 ` Paul Walmsley
2014-07-29 19:37 ` Paul Walmsley
2014-07-30 5:39 ` Tony Lindgren
2014-07-30 5:39 ` Tony Lindgren
2014-07-30 7:53 ` Paul Walmsley
2014-07-30 7:53 ` Paul Walmsley
2014-07-31 13:11 ` Tony Lindgren
2014-07-31 13:11 ` Tony Lindgren
2014-07-31 19:27 ` Paul Walmsley
2014-07-31 19:27 ` Paul Walmsley
2014-08-01 7:10 ` Tony Lindgren
2014-08-01 7:10 ` Tony Lindgren
2014-08-01 7:52 ` Tony Lindgren
2014-08-01 7:52 ` Tony Lindgren
2014-08-07 22:21 ` Paul Walmsley
2014-08-07 22:21 ` Paul Walmsley
2014-08-08 2:14 ` Felipe Balbi
2014-08-08 2:14 ` Felipe Balbi
2014-08-08 6:11 ` Paul Walmsley
2014-08-08 6:11 ` Paul Walmsley
2014-08-08 14:34 ` Felipe Balbi
2014-08-08 14:34 ` Felipe Balbi
2014-08-08 23:39 ` Paul Walmsley [this message]
2014-08-08 23:39 ` Paul Walmsley
2014-08-09 2:49 ` Felipe Balbi
2014-08-09 2:49 ` Felipe Balbi
2014-08-08 2:29 ` Fabio Estevam
2014-08-08 2:29 ` Fabio Estevam
2014-08-08 6:14 ` Paul Walmsley
2014-08-08 6:14 ` Paul Walmsley
2014-08-09 12:41 ` Ezequiel Garcia
2014-08-09 12:41 ` Ezequiel Garcia
2014-07-31 13:12 ` Tero Kristo
2014-07-31 13:12 ` Tero Kristo
2014-07-29 8:50 ` Paul Walmsley
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=alpine.DEB.2.02.1408082338380.30868@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.