[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180906075434.xa64dy7d6p4yolyi@linutronix.de>
Date: Thu, 6 Sep 2018 09:54:34 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Carsten Emde <C.Emde@...dl.org>,
John Kacur <jkacur@...hat.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Julia Cartwright <julia@...com>,
Daniel Wagner <daniel.wagner@...mens.com>,
tom.zanussi@...ux.intel.com
Subject: Re: [PATCH RT 00/22] Linux 4.14.63-rt41-rc1
On 2018-09-05 08:27:54 [-0400], Steven Rostedt wrote:
> Dear RT Folks,
>
> This is the RT stable review cycle of patch 4.14.63-rt41-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 9/7/2018.
Your tree (v4.14.63) has
80d20d35af1ed ("nohz: Fix local_timer_softirq_pending()")
0a0e0829f9901 ("nohz: Fix missing tick reprogram when interrupting an
inline softirq")
which means that the patch "nohz: Prevent erroneous tick stop
invocations" can be reverted / dropped. It might have clashed during the
emerge of the stable tree.
Sebastian
Powered by blists - more mailing lists