From: Craig Milo Rogers <rogers@isi.edu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] USB patches for 2.6.9-rc1
Date: Fri, 27 Aug 2004 11:30:04 -0700 [thread overview]
Message-ID: <20040827183004.GB24018@isi.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0408262040190.2304@ppc970.osdl.org>
On 04.08.26, Linus Torvalds wrote:
> On Thu, 26 Aug 2004, Craig Milo Rogers wrote:
>
> > On 04.08.26, Greg KH wrote:
> > > Greg Kroah-Hartman:
> > > o USB: rip out the whole pwc driver as the author wishes to have done
> > > o USB: rip the pwc decompressor hooks out of the kernel, as they are a GPL violation
> >
> > The decompressor hooks may be a Linux kernel policy violation,
> > but I challenge your contention that they are a GPL violation.
>
> Doesn't matter. Whether they are a GPL violation is a gray area. They were
> removed because of a policy. The author then complained, and the _driver_
> was removed for that reason.
>
> At no point was it a legal argument. In fact, since none of the people
> involved were layers, you shouldn't even try to _make_ it a legal
> arguments.
Thank you, Linus, for making my point to Greg more clearly
than I did. Saying that the pwc decompressor hooks were removed "as
they are a GPL violation" is a difficult statement to support, and
brings up unresolved legal issues -- exactly what I tried to say. I'm
pleased you've clarified this issue for Greg and the rest of us.
In concordance with Linus' policy statement above, Greg, could
you change your patch attribution to say something like "per kernel
policy", please? If for no other reason than to reduce dissention
among future lkml archive delvers about why the pwc removal took
place? :-)
>
> You do legal arguments in front of a judge. Until you reach that point,
> you do what's right. And I think Greg did what is right.
>
> Now, we can whine all we like about the author being childish, or about
> the fact that since it was GPL'd, the hooks can clearly legally be removed
> regardless of his wishes. That's not what this is all about. There are
> more important things involved.
>
> I repeat: if somebody wants to step up as maintainer, I would certainly be
> more than happy to have a pwc driver, and I bet Greg would be too. But you
> don't just take somebody elses code against his wishes - regardless of
> whether you have the "legal right" or not.
>
> Let's put it this way: if you need to ask a lawyer whether what you do is
> "right" or not, you are morally corrupt. Let's not go there. We don't base
> our morality on law.
>
> Linus
[My apologies to anyone who received this message in duplicate. I
sent a shorter version of it last night, but as I never received it
back from vger and it doesn't appear in the www.uwsg.iu.edu archive,
I assume it was eaten somewhere along the way.]
Craig Milo Rogers
next prev parent reply other threads:[~2004-08-27 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:52 [BK PATCH] USB patches for 2.6.9-rc1 Greg KH
2004-08-27 0:02 ` [linux-usb-devel] " Greg KH
[not found] ` <20040827033709.GC1284@isi.edu>
[not found] ` <Pine.LNX.4.58.0408262040190.2304@ppc970.osdl.org>
2004-08-27 18:30 ` Craig Milo Rogers [this message]
2004-08-27 18:38 ` Greg KH
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=20040827183004.GB24018@isi.edu \
--to=rogers@isi.edu \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@osdl.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