From: "Michael Frank" <mhf@linuxmail.org>
To: pcg@goof.com
Cc: "Pavel Machek" <pavel@suse.cz>,
"Software Suspend - Mailing Lists"
<swsusp-devel@lists.sourceforge.net>,
"kernel list" <linux-kernel@vger.kernel.org>
Date: Mon, 22 Mar 2004 17:18:57 +0800 [thread overview]
Message-ID: <opr49atvpk4evsfm@smtp.pacific.net.th> (raw)
On Mon, 22 Mar 2004 01:29:34 +0100, Pavel Machek <pavel@ucw.cz> wrote:
>
> +/*
> + * Copyright (c) 2000-2002 Marc Alexander Lehmann <pcg@goof.com>
> + *
> + * Redistribution and use in source and binary forms, with or without modifica-
> + * tion, are permitted provided that the following conditions are met:
> + *
> + * 1. Redistributions of source code must retain the above copyright notice,
> + * this list of conditions and the following disclaimer.
> + *
> + * 2. Redistributions in binary form must reproduce the above copyright
> + * notice, this list of conditions and the following disclaimer in the
> + * documentation and/or other materials provided with the distribution.
> + *
> + * 3. The name of the author may not be used to endorse or promote products
> + * derived from this software without specific prior written permission.
>
> lzf compression should go under /lib, not under kernel/power, and
> probably should go in separately.
>
> This looks like BSD with advertising clause. I do not think you are
> allowed to link this with kernel. It does not follow kernel coding style.
Hello Marc,
As you will be aware, everone using swsusp2 loves to use your LZF functionality
which yields effective suspend/resume transfer rates of well above 100MB/s.
With inclusion of swsusp2 into kernel mainline drawing nearer, one _major_
issue was raised, which is the BSD license you released LZF under.
As said, BSD-only licensed code is _invalid_ to be linked with kernel code,
therefor swsusp2 will have to drop LZF alltogether unless you relicense it.
Would you please consider to relicense under GPL2, or GPL2 + BSD.
Intel does something like GPL2 + BSD this with ACPI btw. Please have a look
at their license.
This means in practice that GPL2 allows inclusion into the kernel, which
being opensource credits you, and other proprietary apps using the BSD
license will credit you in their documentation.
Also, as Pavel mentioned, LZF code should be put in /lib and cleaned up. This
is a chance to get LZF into the kernel and it would be much appreciated if you
please would take care of this. Thank you!
Regards
Michael
next reply other threads:[~2004-03-22 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 9:18 Michael Frank [this message]
2004-03-22 9:40 ` [Swsusp-devel] " Cameron Patrick
2004-03-22 9:49 ` Arjan van de Ven
2004-03-22 10:02 ` LZF inclusion in kernel Michael Frank
2004-03-22 18:21 ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-23 11:47 ` Arjan van de Ven
2004-03-25 15:02 ` Marc Lehmann
2004-03-24 22:20 ` Nigel Cunningham
2004-03-22 10:15 ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 14:26 ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-25 14:56 ` Pavel Machek
2004-03-28 0:43 ` Marc Lehmann
2004-03-25 15:18 ` [Swsusp-devel] (no subject) Marc Lehmann
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=opr49atvpk4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=pcg@goof.com \
--cc=swsusp-devel@lists.sourceforge.net \
/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
Powered by JetHome