From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: [PATCH RT 0/2] [ANNOUNCE] 3.0.41-rt62-rc1 stable review
Date: Fri, 24 Aug 2012 23:49:00 -0400 [thread overview]
Message-ID: <20120825034900.144648579@goodmis.org> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 3.0.41-rt62-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release candidate).
The pre-releases will not be pushed to the git repository, only the
final release is.
If all goes well, this patch will be converted to the next main release
on 8/29/2012 (again on the late Michael Jackson's B-day, and my
buddy Derek's)
Enjoy,
-- Steve
To build 3.0.41-rt62-rc1 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.xz
http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.41.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/patch-3.0.41-rt62-rc1.patch.xz
You can also build from 3.0.41-rt61 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/incr/patch-3.0.41-rt61-rt62-rc1.patch.xz
Changes from 3.0.41-rt61:
---
Frank Rowand (1):
fix printk flush of messages
Steven Rostedt (1):
Linux 3.0.41-rt62-rc1
----
kernel/printk.c | 2 +-
localversion-rt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2012-08-25 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 3:49 Steven Rostedt [this message]
2012-08-25 3:49 ` [PATCH RT 1/2] fix printk flush of messages Steven Rostedt
2012-08-25 3:49 ` [PATCH RT 2/2] Linux 3.0.41-rt62-rc1 Steven Rostedt
2012-08-27 8:15 ` [PATCH RT 0/2] [ANNOUNCE] 3.0.41-rt62-rc1 stable review Michael Thalmeier
2012-08-27 22:54 ` Frank Rowand
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=20120825034900.144648579@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).