From: Matt Mackall <mpm@selenic.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Clay Haapala <chaapala@cisco.com>,
James Morris <jmorris@redhat.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
"David S. Miller" <davem@redhat.com>
Subject: Re: [PATCH 2.6.1 -- take two] Add CRC32C chksums to crypto and lib routines
Date: Tue, 3 Feb 2004 17:37:37 -0600 [thread overview]
Message-ID: <20040203233737.GD31138@waste.org> (raw)
In-Reply-To: <20040203172508.B26222@lists.us.dell.com>
On Tue, Feb 03, 2004 at 05:25:08PM -0600, Matt Domsch wrote:
> > >> +MODULE_LICENSE("GPL and additional rights");
> > >
> > > "additional rights?"
> > >
> > Take it up with Matt_Domsch@dell.com -- it's his code that I
> > cribbed, so that's the license line I used.
>
> The crc32 code came from linux@horizon.com with the following
> copyright abandonment disclaimer, which is still in lib/crc32.c:
>
> /*
> * This code is in the public domain; copyright abandoned.
> * Liability for non-performance of this code is limited to the amount
> * you paid for it. Since it is distributed for free, your refund will
> * be very very small. If it breaks, you get to keep both pieces.
> */
>
> Thus GPL plus additional rights is appropriate.
Ok, makes sense for CRC32 stuff which can be easily lifted from the
kernel or 50 other places, but not for stuff that's depends on
cryptoapi.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2004-02-03 23:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 21:31 [PATCH] Add CRC32C chksums to crypto routines Clay Haapala
2004-01-14 21:45 ` James Morris
2004-01-14 22:12 ` Clay Haapala
2004-01-16 1:40 ` Matt Mackall
2004-01-19 20:13 ` James Morris
2004-01-19 21:15 ` Clay Haapala
2004-01-19 21:33 ` James Morris
2004-02-03 16:58 ` [PATCH 2.6.1] Add CRC32C chksums to crypto and lib routines Clay Haapala
2004-02-03 17:09 ` James Morris
2004-02-04 17:07 ` Clay Haapala
2004-02-03 17:13 ` James Morris
2004-02-03 17:50 ` [PATCH 2.6.1 -- take two] " Clay Haapala
2004-02-03 18:51 ` Matt Mackall
2004-02-03 19:13 ` Clay Haapala
2004-02-03 19:27 ` Matt Mackall
2004-02-03 20:17 ` James Morris
2004-02-03 23:25 ` Matt Domsch
2004-02-03 23:37 ` Matt Mackall [this message]
2004-02-04 16:14 ` Clay Haapala
2004-02-04 17:21 ` Matt Mackall
2004-02-07 15:20 ` Matt Domsch
2004-02-18 21:24 ` Matt Domsch
2004-02-18 23:18 ` Matt Domsch
2004-02-06 23:54 ` Jamie Lokier
2004-02-04 2:18 ` James Morris
2004-02-04 3:11 ` 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=20040203233737.GD31138@waste.org \
--to=mpm@selenic.com \
--cc=Matt_Domsch@dell.com \
--cc=chaapala@cisco.com \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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