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>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: [PATCH RT 0/7] Linux 3.8.13.13-rt25-rc1
Date: Thu, 21 Nov 2013 11:59:48 -0500 [thread overview]
Message-ID: <20131121165948.354971355@goodmis.org> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 3.8.13.13-rt25-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 11/25/2013.
Enjoy,
-- Steve
To build 3.8.13.13-rt25-rc1 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.8.tar.xz
http://www.kernel.org/pub/linux/kernel/v3.x/patch-3.8.13.13.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/3.8/patch-3.8.13.13-rt25-rc1.patch.xz
You can also build from 3.8.13.13-rt24 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.8/incr/patch-3.8.13.13-rt24-rt25-rc1.patch.xz
Changes from 3.8.13.13-rt24:
---
Mike Galbraith (1):
hwlat-detector: Don't ignore threshold module parameter
Sebastian Andrzej Siewior (2):
mm/slub: do not rely on slab_cached passed to free_delayed()
drm: remove preempt_disable() from drm_calc_vbltimestamp_from_scanoutpos()
Steven Rostedt (Red Hat) (1):
Linux 3.8.13.13-rt25-rc1
Thomas Pfaff (1):
genirq: Set the irq thread policy without checking CAP_SYS_NICE
Wolfram Sang (1):
Kind of revert "powerpc: 52xx: provide a default in mpc52xx_irqhost_map()"
Yang Shi (1):
mm/memcontrol: Don't call schedule_work_on in preemption disabled context
----
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 5 ++---
drivers/gpu/drm/drm_irq.c | 7 -------
drivers/misc/hwlat_detector.c | 2 +-
kernel/irq/manage.c | 2 +-
localversion-rt | 2 +-
mm/memcontrol.c | 4 ++--
mm/slub.c | 10 +++++-----
7 files changed, 12 insertions(+), 20 deletions(-)
next reply other threads:[~2013-11-21 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 16:59 Steven Rostedt [this message]
2013-11-21 16:59 ` [PATCH RT 1/7] genirq: Set the irq thread policy without checking CAP_SYS_NICE Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 2/7] Kind of revert "powerpc: 52xx: provide a default in mpc52xx_irqhost_map()" Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 3/7] hwlat-detector: Dont ignore threshold module parameter Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 4/7] mm/slub: do not rely on slab_cached passed to free_delayed() Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 5/7] mm/memcontrol: Dont call schedule_work_on in preemption disabled context Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 6/7] drm: remove preempt_disable() from drm_calc_vbltimestamp_from_scanoutpos() Steven Rostedt
2013-11-21 16:59 ` [PATCH RT 7/7] Linux 3.8.13.13-rt25-rc1 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=20131121165948.354971355@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--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).