mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "pradeep singh rautela" <rautelap@gmail.com>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: "Greg KH" <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [Q]Can a file be dual licensed in upstream kernel?
Date: Tue, 29 Apr 2008 12:01:55 +0530	[thread overview]
Message-ID: <6bc632150804282331t191abb47gec8bc2e075739a4f@mail.gmail.com> (raw)
In-Reply-To: <20080429062627.GA3195@local>

On Tue, Apr 29, 2008 at 11:56 AM, Hans J. Koch <hjk@linutronix.de> wrote:
> On Tue, Apr 29, 2008 at 11:40:26AM +0530, pradeep singh rautela wrote:
>  > On Tue, Apr 29, 2008 at 11:23 AM, Greg KH <greg@kroah.com> wrote:
>  > > On Tue, Apr 29, 2008 at 11:07:37AM +0530, pradeep [snip]
>  > >  > Can a module/file be Dual licensed(i.e BSD/GPLv2) in the upstream
>  > >  > Linux kernel sources?
>  > >
>  > >  Are you somehow not believing the files that we have in the tree that
>  > >  are licensed this way?
>  > >  > I think it is GPLv2 only.
>  > >
>  > >  Licensing questions would be better off asked to lawyers, not
>  > >  programmers.  Would you ask a random group of lawyers on a public
>  > >  mailing list medical questions and trust their responses?
>  >
>  > Um... apologies Greg.I did not mean that in any sense.I am a
>  > programmer not a lawyer. I am asking to get clear understanding of the
>  > licensing issues and I myself do not have any good understanding on
>  > dual licensing Vs GPLv2 licensing in Linux kernel.
>
>  I share Greg's opinion that this list is not the place for getting or
>  giving legal advice. Please _do_ consult a lawyer.
>  In my _personal_opinion_, dual licensing gives you the right to choose
>  between two licenses. If a file is dual licensed BSD/GPLv2, anybody
>  (including yourself) is free to get rid of the BSD part and make it
>  GPLv2 only.

Thanks Hans.That clears things for a newbie like me.

Regards,
    --Pradeep
>
>  Thanks,
>  Hans
>
>



-- 
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

  reply	other threads:[~2008-04-29  6:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29  5:37 pradeep singh rautela
2008-04-29  5:53 ` Greg KH
2008-04-29  6:10   ` pradeep singh rautela
2008-04-29  6:26     ` Hans J. Koch
2008-04-29  6:31       ` pradeep singh rautela [this message]
2008-05-01 14:59       ` David Schwartz
2008-05-14 15:28         ` Pavel Machek
2008-05-14 23:36           ` David Schwartz
2008-05-15 18:23             ` Pavel Machek
2008-04-29  6:33 ` Bart Van Assche
2008-04-29  8:50 ` Alan Cox
2008-04-29  9:16   ` pradeep singh rautela

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=6bc632150804282331t191abb47gec8bc2e075739a4f@mail.gmail.com \
    --to=rautelap@gmail.com \
    --cc=greg@kroah.com \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.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 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®