All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Welling <mwelling@ieee.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] IMX6 Quad inconsistent lock state
Date: Mon, 8 Feb 2016 21:42:58 +0100	[thread overview]
Message-ID: <20160208204258.GC5654@hermes.click-hack.org> (raw)
In-Reply-To: <20160203144724.GA25464@deathstar>

On Wed, Feb 03, 2016 at 08:47:24AM -0600, Michael Welling wrote:
> On Wed, Feb 03, 2016 at 02:51:40AM +0100, Gilles Chanteperdrix wrote:
> > Indeed, I even looked at it. Sorry. It is late here, I will try and
> > use it tomorrow.
> >
> 
> Any luck replicating the build error?

Hi,

I replicate the build error with your .config. The reason why the
build tests do not have the build error is that they enable
CONFIG_XENO_OPT_DEBUG_LOCKING, which disables the "smp-on-up"
optimization for Xenomai locks.

So, we are missing an EXPORT_SYMBOL, or more likely
EXPORT_SYMBOL_GPL in the I-pipe code.

Regards.

-- 
					    Gilles.
https://click-hack.org


  parent reply	other threads:[~2016-02-08 20:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 19:53 [Xenomai] IMX6 Quad inconsistent lock state Michael Welling
2016-02-02 20:02 ` Gilles Chanteperdrix
2016-02-02 20:35   ` Michael Welling
2016-02-02 20:59     ` Gilles Chanteperdrix
2016-02-03  0:32       ` Michael Welling
2016-02-03  0:43         ` Gilles Chanteperdrix
2016-02-03  1:21           ` Michael Welling
2016-02-03  1:31             ` Gilles Chanteperdrix
2016-02-03  1:36               ` Michael Welling
2016-02-03  1:37                 ` Gilles Chanteperdrix
2016-02-03  1:42                   ` Michael Welling
2016-02-03  1:51                     ` Gilles Chanteperdrix
2016-02-03 14:47                       ` Michael Welling
2016-02-03 14:53                         ` Gilles Chanteperdrix
2016-02-08 20:42                         ` Gilles Chanteperdrix [this message]
2016-02-02 22:08     ` Gilles Chanteperdrix

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=20160208204258.GC5654@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=mwelling@ieee.org \
    --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.