From: Scott Lurndal <scott@lurndal.org>
To: travis@sgi.com
Cc: jason.wessel@windriver.com, linux-kernel@vger.kernel.org,
ebiederm@xmission.com
Subject: Re: [PATCH 05/14] KDB: add more exports for supporting KDB modules
Date: Wed, 13 Mar 2013 07:53:02 -0700 [thread overview]
Message-ID: <20130313145302.GA23308@mail.lurndal.org> (raw)
> Looking back at the KDB sources originally posted on oss.sgi.com I
> did not see any restrictions on the use of KDB. How/why was that
> restriction granted and by whom? Was SGI, the original copyright
> owner of KDB, asked or even informed of that decision? I'm not
> trying to be a lawyer here, but someone decided (perhaps wrongly)
> that KDB should only be used by GPL modules.
At the time that I wrote that original KDB code at SGI, there was no
intent to make it only usable by GPL modules. If anything, it was intended
to be more in the BSD-style (anyone can use it any way they like with
attribution) than the GPLv3-style (use it our way, or else).
But then, EXPORT_SYMBOL_GPL didn't exist then. And I think its existence
is silliness on the part of several hard-core developers.
scott lurndal
next reply other threads:[~2013-03-13 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 14:53 Scott Lurndal [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 19:38 [PATCH 00/14] x86/UV/KDB/NMI: Updates for NMI/KDB handler for SGI UV Mike Travis
2013-03-12 19:38 ` [PATCH 05/14] KDB: add more exports for supporting KDB modules Mike Travis
2013-03-12 20:09 ` Eric W. Biederman
2013-03-12 22:03 ` Mike Travis
2013-03-12 22:13 ` Greg Kroah-Hartman
2013-03-12 22:26 ` Mike Travis
2013-03-12 22:39 ` Eric W. Biederman
2013-03-12 23:03 ` Mike Travis
2013-03-12 20:23 ` Greg Kroah-Hartman
2013-03-12 22:01 ` Thomas Gleixner
2013-03-12 22:08 ` Mike Travis
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=20130313145302.GA23308@mail.lurndal.org \
--to=scott@lurndal.org \
--cc=ebiederm@xmission.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=travis@sgi.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
all inboxes | Powered by JetHome®