From: Jaroslav Kysela <perex@perex.cz>
To: alsa-devel@alsa-project.org
Cc: clemens.lang@bmw-carit.de
Subject: Re: Possible GPL-licensed header included in alsa-lib
Date: Tue, 09 Dec 2014 19:40:07 +0100 [thread overview]
Message-ID: <54874207.5030609@perex.cz> (raw)
In-Reply-To: <20141209174917.GC22300@ulm-bmuc496424.bmw-carit.de>
Dne 9.12.2014 v 18:49 Clemens Lang napsal(a):
> Hi,
>
> I recently reviewed the alsa-lib 1.0.27.2 source code from a licensing
> perspective to ensure compliant usage and distribution. It seems the
> intention is for the libraries to be covered by LGPL.
>
> I had a look at include/list.h, which seems to be licensed under
> GPL-2.0. It does not have a license header or any other copyright
> information, but it states it was taken from Linux 2.4.0:
>
> include/list.h, line 5:
> | This code was taken from the Linux 2.4.0 kernel. [jaroslav]
>
> I'm not sure one could argue that the header was trivial, especially
> since it does not only contain constants, structures and interface
> definitions, but also implementations of inline functions.
Fro my view, it's really trivial, but ...
>
> I found one previous inquiry about a similar issue[1], but it does not
> cover the include/list.h header.
>
>
> Two questions:
> 1. Have the copyright holders of the code in question agreed to
> re-license under a different, LGPL-preserving license and, if yes,
> is there some documentation about that?
I don't think so.. Not sure how difficult would be to gather the
original authors from the 2.4 code.
> 2. If the header is indeed covered by GPL-2.0, would you accept patches
> to replace it with a different implementation, e.g. Rusty Russell's
> MIT-licensed list from ccan[2]?
It could be solution, but the current code seems a bit less complicated.
Could you try to obtain list of original authors from linux 2.4 ? I
think I can ask about the licence change.
Thanks,
Jaroslav
>
>
> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2011-March/038267.html
> [2] http://ccodearchive.net/info/list.html
>
>
> Thank you for your time,
> Clemens Lang
>
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2014-12-09 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 17:49 Possible GPL-licensed header included in alsa-lib Clemens Lang
2014-12-09 18:40 ` Jaroslav Kysela [this message]
2014-12-11 8:55 ` Clemens Lang
2015-01-19 14:31 ` Clemens Lang
2015-07-23 16:02 ` Replace include/list.h with non-GPL implementation Clemens Lang
2015-07-23 16:02 ` [PATCH 1/2] Replace list.h with MIT-licensed implementation Clemens Lang
2015-07-23 16:02 ` [PATCH 2/2] Adapt to changes in the linked list API Clemens Lang
2015-07-23 19:03 ` Replace include/list.h with non-GPL implementation Takashi Iwai
2015-07-24 7:34 ` Clemens Lang
2015-07-24 8:13 ` Takashi Iwai
2015-07-24 16:32 ` Takashi Iwai
2015-07-27 9:45 ` Clemens Lang
2015-07-27 9:52 ` Takashi Iwai
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=54874207.5030609@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=clemens.lang@bmw-carit.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.