All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Craig Milo Rogers <rogers@isi.edu>
Cc: Linus Torvalds <torvalds@osdl.org>,
	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:38:31 -0700	[thread overview]
Message-ID: <20040827183831.GA1715@kroah.com> (raw)
In-Reply-To: <20040827183004.GB24018@isi.edu>

On Fri, Aug 27, 2004 at 11:30:04AM -0700, Craig Milo Rogers wrote:
> 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?  :-)

Hm, I can't do that anymore, as Linus has accepted it into his tree
already.  If he feels it's a big issue, he can edit it there.

thanks,

greg k-h

      reply	other threads:[~2004-08-27 18:41 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
2004-08-27 18:38       ` Greg KH [this message]

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=20040827183831.GA1715@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rogers@isi.edu \
    --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 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.