From: Christoph Hellwig <hch@infradead.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Christoph Hellwig <hch@infradead.org>,
davids@webmaster.com, erikharrison@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Thu, 17 Jun 2004 09:47:41 +0100 [thread overview]
Message-ID: <20040617084741.GA28595@infradead.org> (raw)
In-Reply-To: <200406171043.40533.oliver@neukum.org>
On Thu, Jun 17, 2004 at 10:43:40AM +0200, Oliver Neukum wrote:
> Am Donnerstag, 17. Juni 2004 09:59 schrieb Christoph Hellwig:
> > On Thu, Jun 17, 2004 at 12:45:32AM +0200, Oliver Neukum wrote:
> > > This all boils down to the question of whether fimware is code or not.
> >
> > No, that's exactly the political discussion we don't want to discuss here.
> > The keyspan case is worse where a file used in the kernel built has a
> > GPL-incompatible license.
>
> Then go hence and convert the driver to the sysfs firmware interface,
> but please, please take the legalese off this list.
Umm, we ship something that isn't GPL-compatible. Whenever I found
something like that (GFDL documentation, headers from vendor SDKs,
strange license text) we got that solved easily. Now because it's the
magic firmware crap we shouldn't care anymore.
And no, I'm not going to convert it. I'm not a usb person and I couldn't
test it. If one of you usb guys want to convert it that's fine, if we
get the files relicensed under a GPL-compatible license that's fine aswell,
else I'll send a removal patch to Linus.
Stop beeing sloppy about copyrights.
next prev parent reply other threads:[~2004-06-17 8:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:57 more files with licenses that aren't GPL-compatible Christoph Hellwig
2004-06-16 0:38 ` Eric
2004-06-16 1:27 ` Kyle Moffett
2004-06-16 4:11 ` David Schwartz
2004-06-16 20:34 ` Erik Harrison
2004-06-16 20:37 ` Christoph Hellwig
2004-06-16 21:21 ` David Schwartz
2004-06-16 22:45 ` Oliver Neukum
2004-06-16 23:45 ` David Schwartz
2004-06-17 14:09 ` Timothy Miller
2004-06-17 18:35 ` David Schwartz
2004-06-17 19:22 ` Timothy Miller
2004-06-17 7:59 ` Christoph Hellwig
2004-06-17 8:43 ` Oliver Neukum
2004-06-17 8:47 ` Christoph Hellwig [this message]
2004-06-17 10:09 ` Martin Diehl
2004-06-17 10:14 ` Christoph Hellwig
2004-06-19 18:29 ` David Woodhouse
2004-06-17 14:04 ` Timothy Miller
2004-06-16 22:49 ` Helge Hafting
2004-06-18 9:08 ` Adrian Cox
2004-06-18 11:21 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 23:47 Wichmann, Mats D
2004-06-17 1:18 ` Kyle Moffett
2004-06-18 6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09 ` Adam J. Richter
2004-06-17 19:14 ` Kyle Moffett
2004-06-17 20:51 ` Flavio Stanchina
2004-06-17 20:53 ` Kyle Moffett
2004-06-17 21:05 ` mdpoole
2004-06-17 21:10 ` Christoph Hellwig
2004-06-17 21:45 ` Flavio Stanchina
2004-06-17 20:22 ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54 ` Christoph Hellwig
2004-06-17 20:22 ` Greg KH
2004-06-17 20:30 ` Christoph Hellwig
2004-06-17 20:52 ` Greg KH
2004-06-18 6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole
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=20040617084741.GA28595@infradead.org \
--to=hch@infradead.org \
--cc=davids@webmaster.com \
--cc=erikharrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
/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