From: Vasudev Kamath <vasudev@copyninja.info>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] Using Preempt RT with I-Pipe/Xenomai
Date: Tue, 27 Oct 2015 11:46:03 +0530 [thread overview]
Message-ID: <877fm8x2e4.fsf@copyninja.info> (raw)
In-Reply-To: loom.20151027T063128-689@post.gmane.org
Vasudev Kamath <vasudev@copyninja.info> writes:
> After the patch Kernel did compile, though I've not tested the compiled
> kernel yet. Since I've no idea if what I've done is correct or not I would
> be happy to get some review on this patch from you or fellow Xenomai folks.
>
Err correction, it looks like there are still errors but compilation
didn't stop on errors. Currently I saw following error.
kernel/locking/rtmutex.c: In function _rt_mutex_adjust_prio_chain_:
kernel/locking/rtmutex.c:459:969: error: _spinlock_t_ has no member named _rlock_
kernel/locking/rtmutex.c: In function _rt_spin_lock_slowunlock_hirq_:
kernel/locking/rtmutex.c:1081:971: error: _spinlock_t_ has no member named _rlock_
kernel/locking/rtmutex.c: In function _rt_mutex_slowtrylock_:
kernel/locking/rtmutex.c:1473:969: error: _spinlock_t_ has no member named _rlock_
Will be looking at code now. But it looks like fixing this might be
beyond my expertise. I wonder if Christoph managed to compile kernel
from his side.
Cheers,
next prev parent reply other threads:[~2015-10-27 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 19:59 [Xenomai] Using Preempt RT with I-Pipe/Xenomai Stoidner, Christoph
2014-05-26 11:08 ` Philippe Gerum
2014-05-26 14:11 ` Stoidner, Christoph
2015-10-27 5:43 ` Vasudev Kamath
2015-10-27 6:16 ` Vasudev Kamath [this message]
2015-10-27 11:07 ` Vasudev Kamath
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=877fm8x2e4.fsf@copyninja.info \
--to=vasudev@copyninja.info \
--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.