mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>,
	Fawad Lateef <fawadlateef@gmail.com>,
	jjoy@novell.com, "Nutan C." <nutanc@esntechnologies.co.in>,
	"Mukund JB." <mukundjb@esntechnologies.co.in>,
	gauravd.chd@gmail.com, bulb@ucw.cz, greg@kroah.com,
	Shakthi Kannan <cyborg4k@yahoo.com>
Subject: Re: GPL and NON GPL version modules
Date: Mon, 15 May 2006 17:28:52 +0200	[thread overview]
Message-ID: <1147706948.3013.13.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <AF63F67E8D577C4390B25443CBE3B9F70928E8@esnmail.esntechnologies.co.in>

On Mon, 2006-05-15 at 15:23 +0530, Srinivas G. wrote:
> Dear All,
>  
> I have a small doubt about the GPL and NON GPL version modules.

then you should talk to a lawyer for legal advice

> 
> If I have a module called module A which uses the GPL code and module B
> uses the NON GPL (proprietary) code. If the module A depends on module
> B, is it possible to load these modules? That is some of the functions
> (which are defined in module B) are called from module A.

and explain to him how you created the modules and then ask him a few
questions like

1) at what point does the non-gpl part become a derived work of the gpl
part?
2) can I distribute A and B together, given the clause 2 of the GPL
which may restrict when you can distribute a GPL component with other
stuff?
3) how does the answer to 1) and 2) vary in different countries?
4) will you defend me in court if I follow your advice?
  (eg how sure are you of your answers)

and then listen really carefully to what your lawyer has to say on these
points, and then and only then make your own decision, based on what he
says, if you want to go forward with what you describe.



  parent reply	other threads:[~2006-05-15 15:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- 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 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: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=1147706948.3013.13.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=bulb@ucw.cz \
    --cc=cyborg4k@yahoo.com \
    --cc=fawadlateef@gmail.com \
    --cc=gauravd.chd@gmail.com \
    --cc=greg@kroah.com \
    --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 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®