linux-kernel - Re: [PATCH 2/2] usb: clean up FSF boilerplate text

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]

Message-ID: <4E6E58C9.7090901@sensortherm.de>
Date:	Mon, 12 Sep 2011 21:08:57 +0200
From:	Klaus Schwarzkopf <schwarzkopf@...sortherm.de>
To:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, Greg KH <gregkh@...e.de>,
	mina86@...a86.com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] usb: clean up FSF boilerplate text

Am 12.09.2011 19:24, schrieb Sarah Sharp:
> 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@...e.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@...sortherm.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. :)
>

Sorry, was 52 recipient, and i wouldn't spam the list.

> Sarah Sharp

My proposals:

1. do nothing, very easy ;-)
2. change the old address to the new one
3. remove the address paragraph and add the following text (from 
http://www.gnu.org/licenses/gpl.html):

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.


possibly change the url to, e.g. http://kernel.org/gpl2.txt

Regards,

Klaus Schwarzkopf







--
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/