mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Juerg Haefliger <juergh@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [ANNOUNCE] 3.14.43-rt42
Date: Thu, 18 Jun 2015 09:58:07 -0400	[thread overview]
Message-ID: <20150618095807.68448b49@gandalf.local.home> (raw)
In-Reply-To: <CADLDEKstKq87vKsk2P+3jMYyha2B+gewBt6+_OwMy63PFAK_bw@mail.gmail.com>

On Thu, 18 Jun 2015 09:26:59 +0200
Juerg Haefliger <juergh@gmail.com> wrote:

> Hi Steve,
> 
> On Thu, May 21, 2015 at 5:24 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Dear RT Folks,
> >
> > I'm pleased to announce the 3.14.43-rt42 stable release.
> >
> >
> > This release is just an update to the new stable 3.14.43 version
> > and no RT specific changes have been made.
> >
> >
> > You can get this release via the git tree at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> 
> This kernel doesn't compile with CONFIG_NO_HZ_FULL:
> 
> kernel/time/tick-sched.c: In function ‘can_stop_full_tick’:
> kernel/time/tick-sched.c:183:2: error: implicit declaration of
> function ‘arch_irq_work_has_interrupt’
> [-Werror=implicit-function-declaration]
>   if (!arch_irq_work_has_interrupt()) {
>   ^
>   CC      mm/pgtable-generic.o
> cc1: some warnings being treated as errors
> scripts/Makefile.build:308: recipe for target 'kernel/time/tick-sched.o' failed
> make[2]: *** [kernel/time/tick-sched.o] Error 1
> scripts/Makefile.build:455: recipe for target 'kernel/time' failed
> make[1]: *** [kernel/time] Error 2
> 
> 
> arch_irq_work_has_interrupt wasn't introduced until 3.17-rc5 with
> commit c5c38ef3d70377dc504a6a3f611a3ec814bc757b.
> 
> Patch 0353-kernel-irq_work-fix-no_hz-deadlock.patch breaks the build.

Thanks for letting me know. I need to work on the stable releases again
soon. If not this week, I'll do it first thing next week.

-- Steve


> 
> ...Juerg
> 
> 
>

      reply	other threads:[~2015-06-18 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  3:24 Steven Rostedt
2015-06-18  7:26 ` Juerg Haefliger
2015-06-18 13:58   ` Steven Rostedt [this message]

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=20150618095807.68448b49@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=juergh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®