[PATCH RT 0/7] Linux 3.8.13.13-rt25-rc1

From: Steven Rostedt
Date: Thu Nov 21 2013 - 12:01:26 EST



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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/