linux-kernel - Re: About closed-source module use GPL module function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f020801292352m13d34f36i3f4d930534ffa805@mail.gmail.com>
Date:	Wed, 30 Jan 2008 09:52:50 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"CooperYuan Cooper" <cooperyuan@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: About closed-source module use GPL module function

Hi,

On Jan 30, 2008 8:41 AM, CooperYuan Cooper <cooperyuan@...il.com> wrote:
> Now I am porting a device driver to Linux, its source code is not opened.
>
> In this module, I use some interface functions exported from GPL
> module through EXPORT_SYMBOL macros. (not EXPORT_SYMBOL_GPL), For
> example, register_sound_dsp() and so on.
>
> Do I violate GPL? How to solve it?

This list is probably a not good source for (free) legal advice but
the simplest way to be sure is to release the source code under GPLv2.
HTH.

                        Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/