From: Andrew Morton <akpm@osdl.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, mochel@digitalimplant.org
Subject: Re: Please open sysfs symbols to proprietary modules
Date: Fri, 4 Feb 2005 01:20:42 -0800 [thread overview]
Message-ID: <20050204012042.6aedcf39.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0502021723280.5515@localhost.localdomain>
Pavel Roskin <proski@gnu.org> wrote:
>
> I'm writing a module under a proprietary license.
You shouldn't, although many people do. It's a derived work and hence the
GPL is applicable. The only exception we make is for code which was
written for other operating systems and was then ported to Linux. Because
it is inappropriate to consider such code a derived work.
next prev parent reply other threads:[~2005-02-04 9:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 22:56 Pavel Roskin
2005-02-02 23:07 ` Greg KH
2005-02-02 23:23 ` Patrick Mochel
2005-02-02 23:29 ` Greg KH
2005-02-03 0:07 ` Pavel Roskin
2005-02-03 0:30 ` Greg KH
2005-02-03 4:54 ` Zan Lynx
2005-02-03 5:07 ` Greg KH
2005-02-03 8:59 ` Helge Hafting
2005-02-03 15:12 ` Alan Cox
2005-02-03 17:26 ` Theodore Ts'o
2005-02-03 13:47 ` linux-os
2005-02-04 16:05 ` David Woodhouse
2005-02-03 0:09 ` Joseph Pingenot
2005-02-03 1:13 ` Pavel Roskin
2005-02-03 2:50 ` Kyle Moffett
2005-02-03 3:17 ` Jon Masters
2005-02-06 7:24 ` Lee Revell
2005-02-07 16:05 ` Chris Friesen
2005-02-07 16:55 ` linux-os
2005-02-07 18:58 ` jerome lacoste
2005-02-07 19:35 ` linux-os
2005-02-07 16:55 ` Randy.Dunlap
2005-02-08 1:40 ` Horst von Brand
2005-02-03 4:57 ` Greg KH
2005-02-03 8:41 ` Arjan van de Ven
2005-02-03 21:00 ` Ben Greear
2005-02-04 9:20 ` Andrew Morton [this message]
2005-02-04 9:40 ` Arjan van de Ven
2005-02-15 1:41 ` Alan Cox
2005-02-03 4:08 Jonathan A. George
2005-02-03 5:07 ` Kyle Moffett
2005-02-03 12:30 Jonathan A. George
2005-02-04 15:16 ` Adrian Bunk
2005-02-17 23:13 parker
2005-02-18 3:32 ` Chris Friesen
2005-02-18 13:13 ` Arjan van de Ven
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=20050204012042.6aedcf39.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=proski@gnu.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®