From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Nutan C." <nutanc@esntechnologies.co.in>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>,
Fawad Lateef <fawadlateef@gmail.com>,
jjoy@novell.com, "Mukund JB." <mukundjb@esntechnologies.co.in>,
gauravd.chd@gmail.com, bulb@ucw.cz, greg@kroah.com,
Shakthi Kannan <cyborg4k@yahoo.com>,
"Srinivas G." <srinivasg@esntechnologies.co.in>
Subject: RE: GPL and NON GPL version modules
Date: Mon, 15 May 2006 15:12:32 +0100 [thread overview]
Message-ID: <1147702352.26686.24.camel@localhost.localdomain> (raw)
In-Reply-To: <AF63F67E8D577C4390B25443CBE3B9F7092952@esnmail.esntechnologies.co.in>
On Llu, 2006-05-15 at 19:04 +0530, Nutan C. wrote:
> 1. I developed a code which interfaces well with a proprietary OS. Now,
> somebody else feels to use the same module in his Linux Kernel. So, he
> comes up with a patch, which interfaces and talks to my module with my
> interfaces and then makes a release with the patch. And, I would have no
> idea of my module being really compatible/used in Linux Kernel. One fine
> day, I would get a mail saying that I need to make my code open source.
> What would be my reply?
Probably not polite
If someone takes your proprietary code and combines it with GPL code in
a way the GPL license prohibits then they not you are committing the
license violation (they are probably also violating your license as well
as the GPL license by doing so)
There are exceptions to that - one might be if you developed the code
and arranged for the person to do the merge with Linux rather than
someone else doing it.
In the normal case of things I can combine two works only if the
licenses of the two works are compatible, that is effectively only if I
have permission from all parties who own rights on the resulting
"derivative" work.
Alan
next prev parent reply other threads:[~2006-05-15 14:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 13:34 GPL and NON GPL version modules Nutan C.
2006-05-15 13:41 ` Steven Rostedt
2006-05-15 13:49 ` Steven Rostedt
2006-05-15 14:12 ` Alan Cox [this message]
2006-05-16 3:42 ` David Schwartz
2006-05-16 8:52 ` Xavier Bestel
2006-05-16 19:54 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 14:05 Nutan C.
2006-05-15 14:00 Nutan C.
2006-05-15 14:13 ` Steven Rostedt
2006-05-15 15:12 ` Jan Engelhardt
2006-05-15 12:12 Nutan C.
2006-05-15 12:51 ` Xavier Bestel
2006-05-15 12:52 ` Xavier Bestel
2006-05-15 13:06 ` Steven Rostedt
2006-05-15 9:53 Srinivas G.
2006-05-15 12:54 ` Manu Abraham
2006-05-15 14:14 ` Alan Cox
2006-05-15 15:08 ` Greg KH
2006-05-15 15:49 ` Steven Rostedt
2006-05-15 15:28 ` Arjan van de Ven
2006-05-15 9:31 Srinivas G.
2006-05-15 12:08 ` Jan Engelhardt
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=1147702352.26686.24.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bulb@ucw.cz \
--cc=cyborg4k@yahoo.com \
--cc=fawadlateef@gmail.com \
--cc=gauravd.chd@gmail.com \
--cc=greg@kroah.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jjoy@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukundjb@esntechnologies.co.in \
--cc=nutanc@esntechnologies.co.in \
--cc=rostedt@goodmis.org \
--cc=srinivasg@esntechnologies.co.in \
/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.