mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "pradeep singh rautela" <rautelap@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q]Can a file be dual licensed in upstream kernel?
Date: Tue, 29 Apr 2008 14:46:18 +0530	[thread overview]
Message-ID: <6bc632150804290216j434e51fel255e7f76b0a50b0b@mail.gmail.com> (raw)
In-Reply-To: <20080429095015.2e05f470@core>

On Tue, Apr 29, 2008 at 2:20 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Tue, 29 Apr 2008 11:07:37 +0530
>
> "pradeep singh rautela" <rautelap@gmail.com> wrote:
>
>
> > Hi All,
>  >
>  > A small query.
>  > Can a module/file be Dual licensed(i.e BSD/GPLv2) in the upstream
>  > Linux kernel sources?
>
>  The copy you submit to the kernel needs to be GPL. How you choose to
>  licence it in addition is your business (assuming it is all your own
>  work). Various drivers in the kernel (eg much of infiniband and ACPI) are
>  issued by their authors with multiple licences for different projects.

Thank you for kind explanation, Alan.
That helped a lot.

Regards,
   --Pradeep
>
>  Alan
>



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

      reply	other threads:[~2008-04-29  9:16 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
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 [this message]

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=6bc632150804290216j434e51fel255e7f76b0a50b0b@mail.gmail.com \
    --to=rautelap@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®