linux-kernel - LTTng 0.164: LGPL v2.1 / GPL v2 relicensing phase 1

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>] [day] [month] [year] [list]

Message-ID: <20091023182527.GA15389@Krystal>
Date:	Fri, 23 Oct 2009 14:25:27 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	ltt-dev@...ts.casi.polymtl.ca
Cc:	linux-kernel@...r.kernel.org, David Wilder <dwilder@...ibm.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Robert Wisniewski <bob@...son.ibm.com>
Subject: LTTng 0.164: LGPL v2.1 / GPL v2 relicensing phase 1

Hi,

The LTTng 0.164 release relicenses to dual LGPL v2.1 / GPL v2 license:

* tracer C files (1)
* tracer headers (1)
* immediate values C files (2)

And relicenses to dual BSD / GPL v2 license:

* immediate values headers (2)

(1) except include/linux/ltt-relay.h and ltt/ltt-relay-alloc.c, waiting
    for IBM approval for re-licensing code from kernel/relay.c to
    LGPLv2.1 / GPLv2 dual license.
(2) except sparc 64 support, waiting for approval from David S. Miller.

Phase 2 will also include the re-licensing of tracepoints, markers and
sparc64 immediate values as soon as we receive the approval from each
contributor involved (contacted in a different thread). We hope to also
receive approval from IBM to relicense the content of kernel/relay.c,
otherwise we will rewrite the parts we have used.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/