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>,
Julia Cartwright <julia@ni.com>,
Daniel Wagner <daniel.wagner@siemens.com>,
tom.zanussi@linux.intel.com
Subject: [PATCH RT 0/6] Linux 4.19.37-rt20-rc1
Date: Fri, 24 May 2019 23:32:32 -0400 [thread overview]
Message-ID: <20190525033232.795741612@goodmis.org> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 4.19.37-rt20-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 5/28/2019.
Enjoy,
-- Steve
To build 4.19.37-rt20-rc1 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz
http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.19.37.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/patch-4.19.37-rt20-rc1.patch.xz
You can also build from 4.19.37-rt19 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/incr/patch-4.19.37-rt19-rt20-rc1.patch.xz
Changes from 4.19.37-rt19:
---
Corey Minyard (1):
sched/completion: Fix a lockup in wait_for_completion()
Julien Grall (1):
tty/sysrq: Convert show_lock to raw_spinlock_t
Sebastian Andrzej Siewior (3):
powerpc/pseries/iommu: Use a locallock instead local_irq_save()
powerpc: reshuffle TIF bits
drm/i915: Don't disable interrupts independently of the lock
Steven Rostedt (VMware) (1):
Linux 4.19.37-rt20-rc1
----
arch/powerpc/include/asm/thread_info.h | 11 +++++++----
arch/powerpc/kernel/entry_32.S | 12 +++++++-----
arch/powerpc/kernel/entry_64.S | 12 +++++++-----
arch/powerpc/platforms/pseries/iommu.c | 16 ++++++++++------
drivers/gpu/drm/i915/i915_request.c | 8 ++------
drivers/tty/sysrq.c | 6 +++---
kernel/sched/completion.c | 2 +-
localversion-rt | 2 +-
8 files changed, 38 insertions(+), 31 deletions(-)
next reply other threads:[~2019-05-25 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 3:32 Steven Rostedt [this message]
2019-05-25 3:32 ` [PATCH RT 1/6] powerpc/pseries/iommu: Use a locallock instead local_irq_save() Steven Rostedt
2019-05-25 3:32 ` [PATCH RT 2/6] powerpc: reshuffle TIF bits Steven Rostedt
2019-05-25 3:32 ` [PATCH RT 3/6] tty/sysrq: Convert show_lock to raw_spinlock_t Steven Rostedt
2019-05-25 3:32 ` [PATCH RT 4/6] drm/i915: Dont disable interrupts independently of the lock Steven Rostedt
2019-05-25 3:32 ` [PATCH RT 5/6] sched/completion: Fix a lockup in wait_for_completion() Steven Rostedt
2019-05-25 3:32 ` [PATCH RT 6/6] Linux 4.19.37-rt20-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=20190525033232.795741612@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.