All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code
Date: Wed, 10 Dec 2014 20:45:01 +0100	[thread overview]
Message-ID: <5488A2BD.3080800@xenomai.org> (raw)
In-Reply-To: <20141210191924.GF24110@csclub.uwaterloo.ca>

On 12/10/2014 08:19 PM, Lennart Sorensen wrote:
> On Wed, Dec 10, 2014 at 08:13:50PM +0100, Gilles Chanteperdrix wrote:
>> This is true in user space. Not for kernel modules, see:
>> https://git.xenomai.org/ipipe.git/tree/Documentation/stable_api_nonsense.txt?h=ipipe-3.14
> 
> I can't even figure out how to track down which call is making it
> reference that symbol (for which it has zero interest of course).
> 
> I suppose if whoever made the change in ipipe (which unfortunately the
> ipipe git tree does not make easy to track down since it isn't like it
> is one git tree moving from version to version) does not see the point
> in reverting the change, then I will just have to keep a patch around to
> do it instead and ignore the advisory on the symbol to get this to work.
> I really don't want to do that, but stupid changes sometimes need stupid
> fixes.
> 
> This code does NOT use any xenomai or ipipe features.  Other code does.
> ipipe should not be breaking it.
> 

The stupid guy is me, as the main copyright holder on most of the code
you have been using with Xenomai so far. So where do we go from here?

-- 
Philippe.


  parent reply	other threads:[~2014-12-10 19:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 18:37 [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code Lennart Sorensen
2014-12-10 18:42 ` Gilles Chanteperdrix
2014-12-10 19:02   ` Lennart Sorensen
2014-12-10 19:04     ` Lennart Sorensen
2014-12-10 19:05     ` Gilles Chanteperdrix
2014-12-10 19:09       ` Lennart Sorensen
2014-12-10 19:11         ` Lennart Sorensen
2014-12-10 19:12         ` Gilles Chanteperdrix
2014-12-10 19:13         ` Gilles Chanteperdrix
2014-12-10 19:19           ` Lennart Sorensen
2014-12-10 19:24             ` Gilles Chanteperdrix
2014-12-10 19:39               ` Lennart Sorensen
2014-12-10 19:47                 ` Gilles Chanteperdrix
2014-12-10 19:55                   ` Lennart Sorensen
2014-12-10 19:59                     ` Gilles Chanteperdrix
2014-12-10 20:05                     ` Lennart Sorensen
2014-12-10 19:44             ` Gilles Chanteperdrix
2014-12-10 19:52               ` Lennart Sorensen
2014-12-10 19:57                 ` Gilles Chanteperdrix
2014-12-10 20:12                   ` Lennart Sorensen
2014-12-10 19:45             ` Philippe Gerum [this message]
2014-12-10 19:44               ` Lennart Sorensen
2014-12-10 20:13                 ` Philippe Gerum
2014-12-10 20:11                   ` Lennart Sorensen
2014-12-10 20:38                     ` Philippe Gerum
2014-12-10 21:16                       ` Lennart Sorensen
2014-12-10 21:23                     ` Lennart Sorensen
2014-12-10 21:55                       ` Jeff Webb
2014-12-10 22:01                         ` Lennart Sorensen
2014-12-10 23:18                           ` Jeff Webb
2014-12-10 20:53                   ` Jeff Webb
2014-12-10 21:58                     ` Gilles Chanteperdrix
2014-12-22 10:06                   ` Jan Kiszka
2014-12-22 11:19                     ` Philippe Gerum
2014-12-22 14:46                       ` Lennart Sorensen
2014-12-22 15:00                         ` Philippe Gerum
2014-12-22 19:08                           ` Lennart Sorensen
2014-12-22 14:42                     ` Lennart Sorensen
2014-12-22 14:44                       ` 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=5488A2BD.3080800@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --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.