linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Cartwright <julia@ni.com>
To: <linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Carsten Emde <C.Emde@osadl.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	John Kacur <jkacur@redhat.com>,
	"Paul Gortmaker" <paul.gortmaker@windriver.com>
Subject: [PATCH RT 0/6] Linux 4.1.42-rt50-rc1
Date: Mon, 7 Aug 2017 12:40:56 -0500	[thread overview]
Message-ID: <20170807174102.5448-1-julia@ni.com> (raw)

Dear RT Folks,

This is the RT stable review cycle of patch 4.1.42-rt50-rc1.  Please review
the included patches, and test!

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/14/2017.

   Julia

----------------------------------------------------------------
To build 4.1.42-rt50-rc1 directly, the following patches should be applied:

  http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz

  http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.1.42.xz

  http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/patch-4.1.42-rt50-rc1.patch.xz

You can also build from 4.1.42-rt49 release by applying the incremental patch:

  http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/incr/patch-4.1.42-rt49-rt50-rc1.patch.xz

----------------------------------------------------------------
Alex Shi (1):
  cpu_pm: replace raw_notifier to atomic_notifier

Julia Cartwright (1):
  Linux 4.1.42-rt50-rc1

Peter Zijlstra (2):
  lockdep: Fix per-cpu static objects
  sched: Remove TASK_ALL

Thomas Gleixner (2):
  rtmutex: Make lock_killable work
  sched: Prevent task state corruption by spurious lock wakeup

 include/linux/sched.h    |  1 -
 include/linux/smp.h      | 12 ++++++++++++
 init/main.c              |  8 ++++++++
 kernel/cpu_pm.c          | 43 ++++++-------------------------------------
 kernel/locking/rtmutex.c | 19 +++++++------------
 kernel/module.c          |  6 +++++-
 kernel/sched/core.c      |  2 +-
 localversion-rt          |  2 +-
 mm/percpu.c              |  5 ++++-
 9 files changed, 44 insertions(+), 54 deletions(-)

-- 
2.13.1

             reply	other threads:[~2017-08-07 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 17:40 Julia Cartwright [this message]
2017-08-07 17:40 ` [PATCH RT 1/6] lockdep: Fix per-cpu static objects Julia Cartwright
2017-08-07 17:40 ` [PATCH RT 2/6] rtmutex: Make lock_killable work Julia Cartwright
2017-08-07 17:40 ` [PATCH RT 3/6] sched: Prevent task state corruption by spurious lock wakeup Julia Cartwright
2017-08-07 17:41 ` [PATCH RT 4/6] sched: Remove TASK_ALL Julia Cartwright
2017-08-07 17:41 ` [PATCH RT 5/6] cpu_pm: replace raw_notifier to atomic_notifier Julia Cartwright
2017-08-07 17:41 ` [PATCH RT 6/6] Linux 4.1.42-rt50-rc1 Julia Cartwright

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=20170807174102.5448-1-julia@ni.com \
    --to=julia@ni.com \
    --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=paul.gortmaker@windriver.com \
    --cc=rostedt@goodmis.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).