From: Christoph Hellwig <hch@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Florian Weimer <fw@deneb.enyo.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
Elias Oltmanns <eo@nebensachen.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <clark.williams@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: [PATCH -v2] ftrace: Documentation
Date: Sun, 20 Jul 2008 07:16:01 -0400 [thread overview]
Message-ID: <20080720111601.GA11143@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0807172244100.22792@gandalf.stny.rr.com>
On Thu, Jul 17, 2008 at 10:47:18PM -0400, Steven Rostedt wrote:
> this work, as long as they give me credit (keep the copyright). I don't
> remember exactly how the thread went, I first put the document under the
> GPL, but I someone told me that isn't appropriate for documentation. So I
> used this instead. I know the documentation and the code are distributed
> together, but the "binary" of Linux does not contain the Documentation
> directory as source, so I would think that the GPL is not quite
> appropriate for the Documentation directory.
>
> I'll need to ask a lawyer about this, but how about a "dual" license?
> The GFDL and what ever you feel is appropriate?
The GPL is what covers the whole kernel tree and thuis also te
Documentation/ directory. I don't think we've ever denied anyone to do
any kind of dual licensing as as strange as it might be, so a GPLv2/GFDL
dual license sounds perfectly fine.
next prev parent reply other threads:[~2008-07-20 11:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 16:46 [PATCH] " Steven Rostedt
2008-07-10 18:16 ` Jon Masters
2008-07-10 19:59 ` Elias Oltmanns
2008-07-10 20:28 ` Randy Dunlap
2008-07-11 0:02 ` Steven Rostedt
2008-07-11 0:37 ` [PATCH -v2] " Steven Rostedt
2008-07-11 19:16 ` Andrew Morton
2008-07-11 20:59 ` Steven Rostedt
2008-07-11 22:37 ` Andrew Morton
2008-07-11 23:16 ` Eric W. Biederman
2008-07-15 1:08 ` Steven Rostedt
2008-07-15 1:26 ` Eric W. Biederman
2008-07-15 1:43 ` Steven Rostedt
2008-07-15 1:59 ` Eric W. Biederman
2008-07-15 2:18 ` Steven Rostedt
2008-07-15 2:41 ` Eric W. Biederman
2008-07-15 3:05 ` Steven Rostedt
2008-07-15 3:29 ` Eric W. Biederman
2008-07-12 10:16 ` John Kacur
2008-07-16 10:10 ` Florian Weimer
2008-07-16 11:39 ` Steven Rostedt
2008-07-17 14:19 ` Christoph Hellwig
2008-07-18 2:47 ` Steven Rostedt
2008-07-20 11:16 ` Christoph Hellwig [this message]
2008-07-10 23:55 ` [PATCH] " Steven Rostedt
2008-07-11 7:51 ` Elias Oltmanns
2008-07-12 12:49 ` Abhishek Sagar
2008-07-15 14:39 ` Steven Rostedt
2008-07-15 15:33 ` Abhishek Sagar
2008-07-14 9:38 ` Peter Zijlstra
2008-07-14 18:02 ` David Teigland
2008-07-14 19:59 ` Steven Rostedt
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=20080720111601.GA11143@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=clark.williams@gmail.com \
--cc=eo@nebensachen.de \
--cc=fw@deneb.enyo.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®