From: "Wolfgang M. Reimer" <linuxball@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
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: Re: [PATCH RT 0/7] Linux 3.18.18-rt16-rc1
Date: Fri, 07 Aug 2015 10:47:03 +0200 [thread overview]
Message-ID: <55C47087.7050300@gmail.com> (raw)
In-Reply-To: <20150805011826.881627614@goodmis.org>
Hi all,
only after additionally installing my
"3.18.17-rt14 locktorture: Do NOT include rwlock.h" patch
I could build the kernel with CONFIG_PREEMPT_RT_FULL=y.
So far kernel 3.18.18-rt16-rc1 runs fine on my lenovo
notebook as well as on a server with (an already 5 year
old) ASUS Z8NA-D6(C) motherboard (in Ubuntu 14.04.3 LTS).
Regards,
Wolfgang
On 05.08.2015 03:18, Steven Rostedt wrote:
> Dear RT Folks,
>
> This is the RT stable review cycle of patch 3.18.18-rt16-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 8/10/2015.
>
> Enjoy,
>
> -- Steve
>
>
> To build 3.18.18-rt16-rc1 directly, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.tar.xz
>
> http://www.kernel.org/pub/linux/kernel/v3.x/patch-3.18.18.xz
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.18-rt16-rc1.patch.xz
>
> You can also build from 3.18.18-rt15 by applying the incremental patch:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/3.18/incr/patch-3.18.18-rt15-rt16-rc1.patch.xz
>
>
> Changes from 3.18.18-rt15:
>
> ---
>
>
> Davidlohr Bueso (2):
> futex: Implement lockless wakeups
> ipc/mqueue: Implement lockless pipelined wakeups
>
> Peter Zijlstra (1):
> sched: Implement lockless wake-queues
>
> Sebastian Andrzej Siewior (2):
> Revert "slub: delay ctor until the object is requested"
> kernel/irq_work: fix non RT case
>
> Steven Rostedt (Red Hat) (1):
> Linux 3.18.18-rt16-rc1
>
> Thomas Gleixner (1):
> mm/slub: move slab initialization into irq enabled region
>
> ----
> include/linux/sched.h | 46 ++++++++++++++++++++++++++++
> ipc/mqueue.c | 53 +++++++++++++++++++-------------
> kernel/futex.c | 33 ++++++++++----------
> kernel/sched/core.c | 46 ++++++++++++++++++++++++++++
> kernel/time/timer.c | 3 +-
> localversion-rt | 2 +-
> mm/slub.c | 85 +++++++++++++++++++++++----------------------------
> 7 files changed, 182 insertions(+), 86 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-08-07 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 1:18 [PATCH RT 0/7] Linux 3.18.18-rt16-rc1 Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 1/7] Revert "slub: delay ctor until the object is requested" Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 2/7] mm/slub: move slab initialization into irq enabled region Steven Rostedt
2015-08-10 6:33 ` Mike Galbraith
2015-08-05 1:18 ` [PATCH RT 3/7] sched: Implement lockless wake-queues Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 4/7] futex: Implement lockless wakeups Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 5/7] ipc/mqueue: Implement lockless pipelined wakeups Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 6/7] kernel/irq_work: fix non RT case Steven Rostedt
2015-08-05 1:18 ` [PATCH RT 7/7] Linux 3.18.18-rt16-rc1 Steven Rostedt
2015-08-07 8:47 ` Wolfgang M. Reimer [this message]
2015-08-07 13:48 ` [PATCH RT 0/7] " 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=55C47087.7050300@gmail.com \
--to=linuxball@gmail.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 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.