Re: [PATCH 2.6.1 -- take two] Add CRC32C chksums to crypto and lib routines

[Matt Domsch]

On Wed, Feb 04, 2004 at 11:21:16AM -0600, Matt Mackall wrote:
> As has been pointed out, _not_ putting some sort of license on it
> potentially opens people who ship it up to liability. Arguably, by
> compiling it into the kernel, you're accepting the GPL liability terms
> for that use. But that doesn't stop someone from taking crc32.c,
> incorporating it into something else, having it blow up disastrously,
> and then suing whoever sold them the kernel tarball. Sounds
> outlandish, but crazier things have happened.
> 
> As "dual GPL/public domain license" is an oxymoron, the best thing to
> do is probably to slap a dual GPL/2-clause BSD license on it to
> disclaim liability while minimally limiting all other rights. Matt,
> since you're the last one to touch this, I'll let you make the call,
> but here's what I would suggest (still needs an actual copyright
> notice):

Thanks for the dual-license BSD/GPL patch Matt.
Before proceeding with accepting your patch, I'm asking our Dell IP
legal team for advice, just to be safe.  IANAL, most of us aren't,
they are.  I'll send a follow-up soon as I hear back, probably early
next week.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/