From: Xavier Bestel <Xavier_Bestel@mentor.com>
To: "Nutan C." <nutanc@esntechnologies.co.in>
Cc: 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 14:52:13 +0200 [thread overview]
Message-ID: <1147697533.25330.79.camel@capoeira> (raw)
In-Reply-To: <1147697493.25330.77.camel@capoeira>
On Mon, 2006-05-15 at 14:51, Xavier Bestel wrote:
> On Mon, 2006-05-15 at 14:12, Nutan C. wrote:
> > Hi Jan,
> >
> > So, if the proprietary code exposes an interface and if the code within
> > the GPL makes a call to that interface, will the proprietary code become
> > part of GPL. Please suggest
>
> No, but you don't have permission to redistribute the resulting kernel
> unless the whole code is GPL.
> In short, you can make it but you can't ship it.
BTW, for a real advice consult a real lawyer.
Xav
next prev parent reply other threads:[~2006-05-15 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 12:12 GPL and NON GPL version modules Nutan C.
2006-05-15 12:51 ` Xavier Bestel
2006-05-15 12:52 ` Xavier Bestel [this message]
2006-05-15 13:06 ` Steven Rostedt
-- 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 13:34 Nutan C.
2006-05-15 13:41 ` Steven Rostedt
2006-05-15 13:49 ` Steven Rostedt
2006-05-15 14:12 ` Alan Cox
2006-05-16 3:42 ` David Schwartz
2006-05-16 8:52 ` Xavier Bestel
2006-05-16 19:54 ` David Schwartz
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=1147697533.25330.79.camel@capoeira \
--to=xavier_bestel@mentor.com \
--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=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.