From: Jan Kiszka <jan.kiszka@siemens.com>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] [PULL] ipipe: fixes for 3.14
Date: Mon, 16 Feb 2015 18:35:12 +0100 [thread overview]
Message-ID: <54E22A50.4070106@siemens.com> (raw)
The following changes since commit 00d8a6f2e95453f61ae97b6587dba03bc91c7e1a:
arm/ipipe: Resolve trival merge conflicts (2015-01-14 17:00:22 +0100)
are available in the git repository at:
git://git.xenomai.org/ipipe-jki
for you to fetch changes up to f982e48ce99e1bc9e71eac21830adac2db265c98:
x86/ipipe: Restore invocation of ipipe_unlock_irq from startup_ioapic_irq (2015-02-16 18:22:21 +0100)
All patches apply to 3.16 as well but weren't tested there yet. Still
analyzing strange
traps: (systemd)[1420] trap invalid opcode ip:7f4d138f612b sp:7fff4fd8f568 error:0 in libpthread-2.19.so[7f4d138e5000+18000]
on the target under 3.14...
----------------------------------------------------------------
Jan Kiszka (3):
arm/ipipe: Fix ret_from_exception for !CONFIG_IPIPE
ipipe: Disable PROVE_RCU when I-pipe is on
x86/ipipe: Restore invocation of ipipe_unlock_irq from startup_ioapic_irq
arch/arm/kernel/entry-armv.S | 4 +++-
arch/x86/kernel/apic/io_apic.c | 1 +
lib/Kconfig.debug | 2 +-
3 files changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2015-02-16 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 17:35 Jan Kiszka [this message]
2015-02-16 17:48 ` [Xenomai] [PULL] ipipe: fixes for 3.14 Philippe Gerum
2015-02-16 17:52 ` Jan Kiszka
2015-02-16 18:52 ` Jan Kiszka
2015-02-16 19:11 ` Jan Kiszka
2015-02-16 19:35 ` Philippe Gerum
2015-02-16 20:15 ` Jan Kiszka
2015-02-17 14:49 ` Jan Kiszka
2015-02-17 17:27 ` Jan Kiszka
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=54E22A50.4070106@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.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 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.