From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Neil Bradley <neil.bradley@windowslive.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.18.9-rt4
Date: Mon, 16 Mar 2015 18:50:42 +0100 [thread overview]
Message-ID: <20150316175042.GE28130@linutronix.de> (raw)
In-Reply-To: <loom.20150309T235034-919@post.gmane.org>
* Neil Bradley | 2015-03-09 22:54:54 [+0000]:
>Hi there.
Hi,
>
>If I compile the rt patch with any pre-emption model other than full
>preemption, I get a compile error in kernel/irq_work:150:20.
>hirq_work_list Undeclared.
>
>Using current 3.18.9 sources & patch-3.18.9-rt4.
thx, Steven sent a fix, will be fixed in the next release.
>Cheers, Neil.
Sebastian
prev parent reply other threads:[~2015-03-16 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 14:15 [ANNOUNCE] 3.18.9-rt4 Sebastian Andrzej Siewior
2015-03-07 15:25 ` Gustavo Bittencourt
2015-03-07 23:12 ` Uwe Kleine-König
2015-03-09 22:54 ` Neil Bradley
2015-03-16 17:50 ` Sebastian Andrzej Siewior [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=20150316175042.GE28130@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=neil.bradley@windowslive.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 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).