linux-kernel - Re: [PATCH] USB: mark USB drivers as being GPL only

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 9 Feb 2008 19:29:37 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Christer Weinigel" <christer@...nigel.se>
Cc:	"Hans-Jürgen Koch" <hjk@...utronix.de>,
	"David Newall" <davidn@...idnewall.com>,
	"Marcel Holtmann" <marcel@...tmann.org>,
	"Diego Zuccato" <diego@...llo.alma.unibo.it>,
	"Greg KH" <greg@...ah.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only

On Feb 9, 2008 6:50 PM, Christer Weinigel <christer@...nigel.se> wrote:
> A device driver isn't that hard either.  I can write a device driver
> with a hand tied behind my back, to write a good balancing tree, I'd
> have to spend a lot more time reading up on algorithms.  So "trivial" is
> a matter of background.

It doesn't matter how "hard" it was to write that code. What matters
is whether your code requires enough copyrighted aspects of the
original work to constitute as derived work. There's a huge difference
between using kmalloc and spin_lock and writing a driver that is built
on to of the full USB stack of Linux kernel, for example.
--
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/