From: Pavel Machek <pavel@ucw.cz>
To: Michael Frank <mhf@linuxmail.org>,
pcg@goof.com,
Software Suspend - Mailing Lists
<swsusp-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] (no subject)
Date: Mon, 22 Mar 2004 11:15:54 +0100 [thread overview]
Message-ID: <20040322101554.GB273@elf.ucw.cz> (raw)
In-Reply-To: <20040322094053.GO16890@patrick.wattle.id.au>
Hi!
> | >+ * 3. The name of the author may not be used to endorse or promote products
> | >+ * derived from this software without specific prior written permission.
> [...]
> | >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.
> [...]
> | 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.
>
> The licence above looks like BSD /without/ advertising clause, which
> is GPL compatible. Note that the (GPL-incompatible) advertising
Yes, I was wrong. It indeed looks like BSD _without_
advertising.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-22 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 9:18 Michael Frank
2004-03-22 9:40 ` [Swsusp-devel] (no subject) 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 ` Pavel Machek [this message]
2004-03-25 14:26 ` 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=20040322101554.GB273@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--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