lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e108260804282333hefda3e1p485391d65a58fa21@mail.gmail.com>
Date:	Tue, 29 Apr 2008 08:33:37 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"pradeep singh rautela" <rautelap@...il.com>
Cc:	linux-kernel@...r.kernel.org, "Greg Kroah-Hartman" <greg@...ah.com>
Subject: Re: [Q]Can a file be dual licensed in upstream kernel?

On Tue, Apr 29, 2008 at 7:37 AM, pradeep singh rautela
<rautelap@...il.com> wrote:
>  A small query.
>  Can a module/file be Dual licensed(i.e BSD/GPLv2) in the upstream
>  Linux kernel sources?
>  I think it is GPLv2 only.
>
>  So does this means any dual licensed files should be aptly GPLv2 only?

There are already source files in the Linux kernel that are dual
licensed. See e.g. drivers/infiniband/core/verbs.c. Note: not all
licenses are compatible. License compatibility is indeed not a topic
for the LKML mailing list.

Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ