public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH RT 0/6] Linux 4.4.27-rt38-rc1
Date: Sun, 30 Oct 2016 12:45:07 -0400	[thread overview]
Message-ID: <20161030164507.542995196@goodmis.org> (raw)


Dear RT Folks,

This is the RT stable review cycle of patch 4.4.27-rt38-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/2/2016.

Enjoy,

-- Steve


To build 4.4.27-rt38-rc1 directly, the following patches should be applied:

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

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

  http://www.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4.27-rt38-rc1.patch.xz

You can also build from 4.4.27-rt37 by applying the incremental patch:

http://www.kernel.org/pub/linux/kernel/projects/rt/4.4/incr/patch-4.4.27-rt37-rt38-rc1.patch.xz


Changes from 4.4.27-rt37:

---


Mike Galbraith (1):
      ftrace: Fix trace header alignment

Sebastian Andrzej Siewior (4):
      kernel/futex: don't deboost too early
      zsmalloc: turn that get_cpu_light() into a local_lock()
      x86/apic: get rid of "warning: 'acpi_ioapic_lock' defined but not used"
      kbuild: add -fno-PIE

Steven Rostedt (Red Hat) (1):
      Linux 4.4.27-rt38-rc1

----
 Makefile                    |  2 +-
 arch/x86/kernel/acpi/boot.c |  2 ++
 include/linux/spinlock.h    |  6 +++++
 include/linux/spinlock_rt.h |  2 ++
 kernel/futex.c              |  2 +-
 kernel/locking/rtmutex.c    | 53 +++++++++++++++++++++++++++++++++++++++------
 kernel/trace/trace.c        | 32 +++++++++++++--------------
 localversion-rt             |  2 +-
 mm/zsmalloc.c               |  6 +++--
 9 files changed, 79 insertions(+), 28 deletions(-)

             reply	other threads:[~2016-10-30 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 16:45 Steven Rostedt [this message]
2016-10-30 16:45 ` [PATCH RT 1/6] kernel/futex: dont deboost too early Steven Rostedt
2016-10-30 16:45 ` [PATCH RT 2/6] ftrace: Fix trace header alignment Steven Rostedt
2016-10-30 16:45 ` [PATCH RT 3/6] zsmalloc: turn that get_cpu_light() into a local_lock() Steven Rostedt
2016-10-30 16:45 ` [PATCH RT 4/6] x86/apic: get rid of "warning: acpi_ioapic_lock defined but not used" Steven Rostedt
2016-10-30 16:45 ` [PATCH RT 5/6] kbuild: add -fno-PIE Steven Rostedt
2016-10-30 16:45 ` [PATCH RT 6/6] Linux 4.4.27-rt38-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=20161030164507.542995196@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=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