public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@suse.de>,
	Klaus Schwarzkopf <schwarzkopf@sensortherm.de>,
	mina86@mina86.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: clean up FSF boilerplate text
Date: Mon, 12 Sep 2011 10:24:07 -0700	[thread overview]
Message-ID: <20110912172407.GA8044@xanatos> (raw)
In-Reply-To: <20110911093625.325b9ea4@lxorguk.ukuu.org.uk>

On Sun, Sep 11, 2011 at 09:36:25AM +0100, Alan Cox wrote:
> On Sun, 11 Sep 2011 02:44:20 +0200
> Greg KH <gregkh@suse.de> wrote:
> 
> > On Sat, Sep 10, 2011 at 10:10:45PM +0100, Alan Cox wrote:
> > > On Sat, 10 Sep 2011 22:24:15 +0200
> > > Klaus Schwarzkopf <schwarzkopf@sensortherm.de> wrote:
> > > 
> > > >     remove the following two paragraphs:
> > > 
> > > NAK this for anything containing my copyright. NAK the one about warranty
> > > and liability because its incredibly important, although of course if
> > > you'd like to take personal liability...
> > 
> > Odd, I was told that if you have the "this is covered under the GPLv2"
> > then that's all that is needed for a single file in a larger body of
> > work, like the kernel.
> 
> People regularly take files out of the kernel or display only one of
> them. However it's a legal question which means changing it needs the
> approval of the right subspecies ....
> 
> You may be right, but it should go past the appropriate expert for the
> change, just like anything else.
> 
> > But you do agree about the address paragraph being able to be removed,
> > right?
> 
> <wears parrot outfit>
> That is a legal question. I am not a lawyer. Please discuss with Intel
> before removing any disclaimers other license material.
> </>
> 
> Sqwark!

Alan's probably right at least about the warranty bit, so I'll have to
NAK for the changes to the xHCI driver (which are copyright Intel).
BTW, it would have been nice to be CC'd on the original patch. :)

Sarah Sharp

  reply	other threads:[~2011-09-12 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10 20:24 [PATCH 2/2] usb: clean up FSF boilerplate text Klaus Schwarzkopf
2011-09-10 20:30 ` Klaus Schwarzkopf
2011-09-10 21:10 ` Alan Cox
2011-09-11  0:44   ` Greg KH
2011-09-11  8:36     ` Alan Cox
2011-09-12 17:24       ` Sarah Sharp [this message]
2011-09-12 19:08         ` Klaus Schwarzkopf
2011-09-12 20:19           ` Alan Cox

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=20110912172407.GA8044@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mina86@mina86.com \
    --cc=schwarzkopf@sensortherm.de \
    /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