From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
Tom Zanussi <tzanussi@gmail.com>,
karim@opersys.com, Michel Dagenais <michel.dagenais@polymtl.ca>,
ltt-dev@lists.casi.polymtl.ca,
Lai Jiangshan <laijs@cn.fujitsu.com>,
kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Robert Wisniewski <bob@watson.ibm.com>
Subject: Re: Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+
Date: Wed, 24 Jun 2009 10:33:34 +0200 [thread overview]
Message-ID: <20090624083334.GB16850@elte.hu> (raw)
In-Reply-To: <20090624004356.GB28911@Krystal>
* Mathieu Desnoyers <compudj@krystal.dyndns.org> wrote:
> Hi,
>
> We want to re-license LTTng as
>
> dual-license GPLv2 (or better)/LGPLv2.1 (or better)
>
> to facilitate code exchange between the GPLv2 LTTng kernel tracer
> and LGPLv2.1 userspace LTTng tracing library. This will also
> include kernel/marker.c, include/linux/marker.h,
> kernel/tracepoint.c and include/linux/tracepoint.h. For the LTTng
> tree, everything under the ltt/ subdirectory is targeted.
>
> I am the main author of most of these files, and I allow such
> license change as far as my code is concerned. Additionally, we
> need the approval of most people who contributed code to either
> LTTng, Linux Kernel Marker and Tracepoints.
Why dont you license the user-space library under the GPLv2?
Also, i dont agree that such interfaces should be ABIs, hence i
oppose the librarization of such raw kernel interfaces. For example
markers will be removed in the future, and tracepoints will sure
undergo more corrective iterations as well.
Ingo
next prev parent reply other threads:[~2009-06-24 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A412702.80707@polymtl.ca>
[not found] ` <20090623191128.GA19010@Krystal>
[not found] ` <20090623191513.GA20253@Krystal>
2009-06-24 0:43 ` Mathieu Desnoyers
2009-06-24 8:33 ` Ingo Molnar [this message]
2009-06-24 14:14 ` Mathieu Desnoyers
2009-06-24 16:33 ` Frank Ch. Eigler
2009-06-24 16:49 ` Mathieu Desnoyers
2009-06-24 17:23 ` Paul E. McKenney
2009-06-29 23:00 ` Mark Wielaard
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=20090624083334.GB16850@elte.hu \
--to=mingo@elte.hu \
--cc=bob@watson.ibm.com \
--cc=compudj@krystal.dyndns.org \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=michel.dagenais@polymtl.ca \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
/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®