From: Ben Finney <bignose@debian.org>
To: Martin Steigerwald <Martin.Steigerwald@proact.de>
Cc: Domenico Andreoli <cavok@debian.org>,
919356@bugs.debian.org, Kristian Fiskerstrand <k_f@gentoo.org>,
Ben Finney <bignose@debian.org>,
Nadia Yvette Chambers <nyc@holomorphy.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"debian-legal\@lists.debian.org" <debian-legal@lists.debian.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: Bug#919356: Licensing of include/linux/hash.h
Date: Tue, 12 Feb 2019 17:27:44 +1100 [thread overview]
Message-ID: <86va1p7c7z.fsf@benfinney.id.au> (raw)
In-Reply-To: <2977287.v5rPGuGa1n@merkaba> (Martin Steigerwald's message of "Mon, 11 Feb 2019 10:50:45 +0000")
Martin Steigerwald <Martin.Steigerwald@proact.de> writes:
> Well the file has in its header:
>
> /* Fast hashing routine for a long.
> (C) 2002 William Lee Irwin III, IBM */
>
> /*
> * Knuth recommends primes in approximately golden ratio to the maximum
> * integer representable by a machine word for multiplicative hashing.
> * Chuck Lever verified the effectiveness of this technique:
> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf
> *
> * These primes are chosen to be bit-sparse, that is operations on
> * them can use shifts and additions instead of multiplications for
> * machines where multiplications are slow.
> */
>
> It has been quite a while ago. I bet back then I did not regard this
> as license information since it does not specify a license. Thus I
> assumed it to be GPL-2 as the other files which have no license boiler
> plate. I.e.: Check file is it has different license, if not, then
> assume it has license as specified in COPYING.
>
> Not specifying a license can however also mean in this context that it
> has no license as the file contains copyright information from another
> author.
If a work (even one file) “has no license”, that means no special
permissions are granted and normal copyright applies: All rights
reserved, i.e. not redistributable. So, no license is grounds to
consider a work non-free and non-redistributable.
If, on the other hand, the file is to be free software, there would need
to be a clear grant of some free software license to that work.
Given the confusion over this file, I would consider it a significant
risk to just assume we have GPLv2 permissions without being told that
explicitly by the copyright holder. Rather, the reason we are seeking a
clearly-granted free license for this one file, is because we are trying
to replace a probably non-free file with the same code in it.
It seems we need to keep looking, and in the meantime assume we have no
free license in this file.
--
\ “If the desire to kill and the opportunity to kill came always |
`\ together, who would escape hanging?” —Mark Twain, _Following |
_o__) the Equator_ |
Ben Finney <bignose@debian.org>
next prev parent reply other threads:[~2019-02-12 6:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 17:00 Domenico Andreoli
2019-01-23 8:50 ` Domenico Andreoli
2019-02-10 23:08 ` Kristian Fiskerstrand
2019-02-11 7:22 ` Domenico Andreoli
2019-02-11 12:43 ` Ulrich Mueller
2019-02-11 14:51 ` Ulrich Mueller
[not found] ` <2977287.v5rPGuGa1n@merkaba>
2019-02-11 22:55 ` Jens Axboe
2019-02-12 6:26 ` Bug#919356: " Ben Finney
2019-02-12 6:27 ` Ben Finney
2019-02-12 6:27 ` Ben Finney [this message]
2019-02-12 16:16 ` Jens Axboe
2019-02-12 17:16 ` [PATCH] Add the SPDX header to include/linux/hash.h Domenico Andreoli
2019-02-12 20:34 ` Bug#919356: Licensing of include/linux/hash.h Martin Steigerwald
2019-02-12 22:08 ` Ben Finney
2019-02-12 20:36 ` Martin Steigerwald
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=86va1p7c7z.fsf@benfinney.id.au \
--to=bignose@debian.org \
--cc=919356@bugs.debian.org \
--cc=Martin.Steigerwald@proact.de \
--cc=acme@redhat.com \
--cc=axboe@kernel.dk \
--cc=cavok@debian.org \
--cc=debian-legal@lists.debian.org \
--cc=jens.axboe@oracle.com \
--cc=k_f@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nyc@holomorphy.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®