From: Steven Rostedt <rostedt@goodmis.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.10.6-rt3
Date: Mon, 12 Aug 2013 21:03:41 -0400 [thread overview]
Message-ID: <20130812210341.4fa2165b@gandalf.local.home> (raw)
In-Reply-To: <CAP=VYLrd_ZU94Nf0X+FtT3M2Xx85t9FF13o-hV+_xHi7EjTf=w@mail.gmail.com>
On Mon, 12 Aug 2013 20:47:18 -0400
Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> On Mon, Aug 12, 2013 at 3:48 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Mon, 12 Aug 2013 18:34:13 +0200
> > Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> >
> >> Dear RT folks!
> >>
> >> I'm pleased to announce the v3.10.6-rt3 patch set.
> >
> >
> > Does this mean that I can drop 3.6-rt in favor of 3.8-rt?
>
> I'd guess that the trade-off would be 3.0-rt against 3.8-rt.
> The above comment assumes 3.0 is aged out vs. 3.6 kernel.
Not at all. I've always said that I would support -rt as long as the
base was supported by the official stable. 3.6 is not supported, and I
only supported it because it was the "latest" stable -rt. When 3.8-rt
comes out, it would also be the latest. But it too is not supported by
the official stable release. I'll only be doing that one until 3.10
becomes stable again. Luckily, 3.8 is being supported by Kamal, and
I'll probably just base my work off of his.
3.0-rt wont last long, as IIRC, Greg will be letting that go off to
ashes in a few months.
>
> >
> > I'm just about finished with a 3.6 stable, which I'll finish, add -rt
> > to it, and then call it "unsupported" after that. Well, I may take bug
> > fixes if people find any in the near future.
> >
> > I'm behind on 3.4-rt, 3.2-rt and of course 3.0-rt. Hopefully, I'll get
> > them all out this week.
>
> I expect that the 3.10-rt kernel will replace the older RT kernels.
No, it will just enter the realm of the official stable releases.
-- Steve
next prev parent reply other threads:[~2013-08-13 1:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:34 Sebastian Andrzej Siewior
2013-08-12 19:48 ` Steven Rostedt
2013-08-13 0:47 ` Paul Gortmaker
2013-08-13 1:03 ` Steven Rostedt [this message]
2013-08-13 1:12 ` Carsten Emde
2013-08-13 10:54 ` Thomas Gleixner
2013-08-13 12:08 ` Steven Rostedt
2013-08-15 18:42 ` Fernando Lopez-Lezcano
2013-08-15 19:22 ` Steven Rostedt
2013-08-15 19:39 ` Fernando Lopez-Lezcano
2013-08-16 7:01 ` Sebastian Andrzej Siewior
2013-08-19 17:23 ` Fernando Lopez-Lezcano
2013-08-20 0:29 ` Steven Rostedt
2013-08-20 0:34 ` Fernando Lopez-Lezcano
2013-08-20 1:02 ` Steven Rostedt
2013-08-20 7:14 ` Sebastian Andrzej Siewior
2013-08-20 14:06 ` Steven Rostedt
2013-08-20 18:58 ` Fernando Lopez-Lezcano
[not found] ` <CAFfPn7iqf5EntPKdRO3cFhd=PFostp3mVLGEtt3ksLQHonMhkw@mail.gmail.com>
2013-08-27 16:19 ` Steven Rostedt
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=20130812210341.4fa2165b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®