From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org, greg@kroah.com,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH stable] ftrace document crucial update
Date: Thu, 31 Jul 2008 11:50:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807311145070.31930@gandalf.stny.rr.com> (raw)
In-Reply-To: <20080731093039.4afcb734@bike.lwn.net>
On Thu, 31 Jul 2008, Jonathan Corbet wrote:
> On Wed, 30 Jul 2008 23:05:02 -0400 (EDT)
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Never mind that ftrace itself doesn't exist is 2.6.26.
s/is/in/ :-(
>
> I just figured you were trying to raise the bar by showing that it's
> possible to get the documentation in before the code...
I'd be impressed if this happens again. ;-)
>
> > Copyright 2008 Red Hat Inc.
> > -Author: Steven Rostedt <srostedt@redhat.com>
> > + Author: Steven Rostedt <srostedt@redhat.com>
> > + License: The GNU Free Documentation License, Version 1.2
>
> Is FDL appropriate for stuff shipped with the kernel? I would suspect
> it would at least need a GPL-compatible dual-license option.
Yeah, Christoph Hellwig brought this up too. I said that I would dual
license it (whatever that means with this) but I wanted to ask a lawyer
first.
The question is, is the FDL really incompatible with the GPL if what is
protected by the FDL does not get compiled and shipped as a binary?
Hence, I need to bring this up with a lawyer. And if it is indeed
incompatible, then I will be sending out a dual license patch.
-- Steve
next prev parent reply other threads:[~2008-07-31 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 3:05 Steven Rostedt
2008-07-31 15:30 ` Jonathan Corbet
2008-07-31 15:50 ` Steven Rostedt [this message]
2008-07-31 16:40 ` [PATCH] dual license ftrace.txt Steven Rostedt
2008-07-31 16:48 ` [PATCH stable] ftrace document crucial update Greg KH
2008-07-31 20:10 ` Steven Rostedt
2008-08-01 23:35 ` Greg KH
2008-07-31 16:53 ` Chris Wright
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=alpine.DEB.1.10.0807311145070.31930@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=chrisw@sous-sol.org \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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®