linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Tonnerre Anklin <thunder@keepsake.ch>
Cc: Kai Germaschewski <kai.germaschewski@gmx.de>,
	Werner Cornelius <werner@isdn4linux.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [I4L] hfcpci missing MODULE_LICENSE
Date: Thu, 27 Nov 2003 22:22:05 -0500	[thread overview]
Message-ID: <200311280322.hAS3M602016305@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 28 Nov 2003 03:00:03 +0100." <20031128020003.GG1635@dbintra.dmz.lightweight.ods.org>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]

On Fri, 28 Nov 2003 03:00:03 +0100, Tonnerre Anklin <thunder@keepsake.ch>  said:

> If this is compiled as a module and then loaded, the kernel is tainted
> because of a missing module license.

True.  However..

> Also,  according to  many european  laws, software  which  is released
> under no license must not be used.

No way to verify this.  I mostly understand the US copyright code as
it impacts my work, but have no idea what the other side of that puddle
does legally (and for that matter, I don't claim to know what the other
side of the other, even bigger, puddle is)...

> <URL:http://keepsake.keepsake.ch/~thunder/noyau/2.6.0-test11-ta1/hfcpci_license.xml>

which says: "I guess the license is meant to be GPL."  And so it was almost
certainly intended to be.

> +MODULE_LICENSE("GPL");
>  MODULE_AUTHOR("Kai Germaschewski <kai.germaschewski@gmx.de>/Werner Cornelius <werner@isdn4linux.de>");


Unfortunately, neither you nor I nor anybody but Kai or Werner (or their
assignees) can do this, as I understand the law.  The only proper resolutions
here are to get one of them to make some sort of statement (I suspect even a
"Yea, it's GPL, we just forgot the macro" e-mail from one of them would be good
enough), or to pull the code out of the 2.6.0 tree till it *is* resolved.

(Sorry to be a stickler, but this is the sort of thing that Darl and
company would love to make a point about - we *do* need to keep careful
track of the actual source and license status of every line....)

Kai? Werner? You out there?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2003-11-28  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28  2:00 [I4L] hfcpci missing MODULE_LICENSE Tonnerre Anklin
2003-11-28  3:22 ` Valdis.Kletnieks [this message]
2003-11-28 23:40   ` Kai Germaschewski
2003-11-28 23:52     ` Valdis.Kletnieks

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=200311280322.hAS3M602016305@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kai.germaschewski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@keepsake.ch \
    --cc=werner@isdn4linux.de \
    /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;
as well as URLs for NNTP newsgroup(s).