From: zanussi@kernel.org
To: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <wagi@monom.org>, Tom Zanussi <zanussi@kernel.org>
Subject: [PATCH RT 0/8] Linux v4.14.172-rt78-rc1
Date: Mon, 9 Mar 2020 14:47:45 -0500 [thread overview]
Message-ID: <cover.1583783251.git.zanussi@kernel.org> (raw)
From: Tom Zanussi <zanussi@kernel.org>
Dear RT Folks,
This is the RT stable review cycle of patch 4.14.172-rt78-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 2020-03-16.
To build 4.14.172-rt78-rc1 directly, the following patches should be applied:
https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.14.tar.xz
https://www.kernel.org/pub/linux/kernel/v4.x/patch-4.14.172.xz
https://www.kernel.org/pub/linux/kernel/projects/rt/4.14/patch-4.14.172-rt78-rc1.patch.xz
You can also build from 4.14.172-rt77 by applying the incremental patch:
https://www.kernel.org/pub/linux/kernel/projects/rt/4.14/incr/patch-4.14.172-rt77-rt78-rc1.patch.xz
Enjoy,
-- Tom
Matt Fleming (1):
mm/memcontrol: Move misplaced local_unlock_irqrestore()
Scott Wood (2):
sched: migrate_enable: Use per-cpu cpu_stop_work
sched: migrate_enable: Remove __schedule() call
Sebastian Andrzej Siewior (4):
userfaultfd: Use a seqlock instead of seqcount
locallock: Include header for the `current' macro
drm/vmwgfx: Drop preempt_disable() in vmw_fifo_ping_host()
tracing: make preempt_lazy and migrate_disable counter smaller
Tom Zanussi (1):
Linux 4.14.172-rt78-rc1
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 2 --
fs/userfaultfd.c | 12 ++++++------
include/linux/locallock.h | 1 +
include/linux/trace_events.h | 3 +--
kernel/sched/core.c | 23 ++++++++++++++---------
kernel/trace/trace_events.c | 4 ++--
localversion-rt | 2 +-
mm/memcontrol.c | 2 +-
8 files changed, 26 insertions(+), 23 deletions(-)
--
2.14.1
next reply other threads:[~2020-03-09 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 19:47 zanussi [this message]
2020-03-09 19:47 ` [PATCH RT 1/8] userfaultfd: Use a seqlock instead of seqcount zanussi
2020-03-09 19:47 ` [PATCH RT 2/8] sched: migrate_enable: Use per-cpu cpu_stop_work zanussi
2020-03-09 19:47 ` [PATCH RT 3/8] sched: migrate_enable: Remove __schedule() call zanussi
2020-03-09 19:47 ` [PATCH RT 4/8] mm/memcontrol: Move misplaced local_unlock_irqrestore() zanussi
2020-03-09 19:47 ` [PATCH RT 5/8] locallock: Include header for the `current' macro zanussi
2020-03-09 19:47 ` [PATCH RT 6/8] drm/vmwgfx: Drop preempt_disable() in vmw_fifo_ping_host() zanussi
2020-03-09 19:47 ` [PATCH RT 7/8] tracing: make preempt_lazy and migrate_disable counter smaller zanussi
2020-03-09 19:47 ` [PATCH RT 8/8] Linux 4.14.172-rt78-rc1 zanussi
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=cover.1583783251.git.zanussi@kernel.org \
--to=zanussi@kernel.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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
/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).