public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Michal Simek <monstr@monstr.eu>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	torvalds@linux-foundation.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	lkml <linux-arch@vger.kernel.org>,
	microblaze-uclinux@itee.uq.edu.au,
	Andrew Morton <akpm@linux-foundation.org>,
	John Williams <john.williams@petalogix.com>,
	John Linn <John.Linn@xilinx.com>,
	Stephen Neuendorffer <stephenn@xilinx.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Peter Korsgaard <jacmet@sunsite.dk>
Subject: Re: [GIT PULL] Microblaze initial pack
Date: Fri, 27 Mar 2009 14:44:34 +0100	[thread overview]
Message-ID: <49CCD842.4050902@petalogix.com> (raw)
In-Reply-To: <20090327122518.GB23023@elte.hu>

Ingo Molnar wrote:
> * Michal Simek <michal.simek@petalogix.com> wrote:
>
>   
>>> I've also done a (quick) license scan and there's this one file i 
>>> found:
>>>
>>>   arch/microblaze/kernel/hw_exception_handler.S
>>>
>>>    * Copyright (C) 2004 Xilinx, Inc. All rights reserved.
>>>    *
>>>    * Xilinx, Inc.
>>>    * XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS" AS A
>>>    * COURTESY TO YOU.BY PROVIDING THIS DESIGN, CODE, OR INFORMATION AS
>>>    * ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE, APPLICATION OR
>>>    * STANDARD, XILINX IS MAKING NO REPRESENTATION THAT THIS IMPLEMENTATION
>>>    * IS FREE FROM ANY CLAIMS OF INFRINGEMENT, AND YOU ARE RESPONSIBLE
>>>    * FOR OBTAINING ANY RIGHTS YOU MAY REQUIRE FOR YOUR IMPLEMENTATION.
>>>
>>> That is an all rights reserved copyrighted file, and i'm not sure 
>>> the above constitutes a GPLv2 compatible license. It would be less 
>>> ambigious to add what you do in the other places instead, something 
>>> like:
>>>
>>>  * (C) Copyright 2004 Xilinx, Inc.
>>>  *
>>>  * This program is free software; you can redistribute it and/or modify it
>>>  * under the terms of the GNU General Public License version 2 as published
>>>  * by the Free Software Foundation.
>>>   
>>>       
>> This is no my license. I'll ask a Xilinx guys for permission to change
>> it for this file.
>> John L, Stephen: Could I change the license as Ingo suggested?
>>     
>
> Note that there's a couple of other Xilinx files in the upstream 
> kernel tree already that could serve as a template:
>
>  drivers/char/xilinx_hwicap/buffer_icap.c: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  drivers/char/xilinx_hwicap/buffer_icap.h: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  drivers/char/xilinx_hwicap/fifo_icap.c: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  drivers/char/xilinx_hwicap/fifo_icap.h: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  drivers/char/xilinx_hwicap/xilinx_hwicap.c: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  drivers/char/xilinx_hwicap/xilinx_hwicap.h: *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>
> Those files carry this as-is no-warrantes notice plus also a GPLv2 
> notice:
>
> /*****************************************************************************
>  *
>  *     Author: Xilinx, Inc.
>  *
>  *     This program is free software; you can redistribute it and/or modify it
>  *     under the terms of the GNU General Public License as published by the
>  *     Free Software Foundation; either version 2 of the License, or (at your
>  *     option) any later version.
>  *
>  *     XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>  *     AS A COURTESY TO YOU, SOLELY FOR USE IN DEVELOPING PROGRAMS AND
>  *     SOLUTIONS FOR XILINX DEVICES.  BY PROVIDING THIS DESIGN, CODE,
>  *     OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
>  *     APPLICATION OR STANDARD, XILINX IS MAKING NO REPRESENTATION
>  *     THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
>  *     AND YOU ARE RESPONSIBLE FOR OBTAINING ANY RIGHTS YOU MAY REQUIRE
>  *     FOR YOUR IMPLEMENTATION.  XILINX EXPRESSLY DISCLAIMS ANY
>  *     WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF THE
>  *     IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
>  *     REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
>  *     INFRINGEMENT, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
>  *     FOR A PARTICULAR PURPOSE.
>  *
>  *     (c) Copyright 2003-2008 Xilinx Inc.
>  *     All rights reserved.
>  *
>  *     You should have received a copy of the GNU General Public License along
>  *     with this program; if not, write to the Free Software Foundation, Inc.,
>  *     675 Mass Ave, Cambridge, MA 02139, USA.
>  *
>  *****************************************************************************/
>
>   
On the base of discussion with John L, I removed old license and I added
GPL one.
All changes which Ingo reported are in git tree.

Do I have to send next (version 2) pull request?
I think that is not necessary.

Thanks,
Michal


> 	Ingo
>   


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

      parent reply	other threads:[~2009-03-27 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  8:11 [GIT PULL] Microblaze initial pack Michal Simek
2009-03-27 10:30 ` Ingo Molnar
2009-03-27 10:40   ` Ingo Molnar
2009-03-27 11:26     ` Michal Simek
2009-03-27 11:36   ` Michal Simek
2009-03-27 12:25     ` Ingo Molnar
     [not found]       ` <20090327122518.GB23023-X9Un+BFzKDI@public.gmane.org>
2009-03-27 13:20         ` John Linn
2009-03-27 13:20           ` John Linn
2009-03-27 13:44       ` Michal Simek [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=49CCD842.4050902@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=John.Linn@xilinx.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=jacmet@sunsite.dk \
    --cc=john.williams@petalogix.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=mingo@elte.hu \
    --cc=monstr@monstr.eu \
    --cc=randy.dunlap@oracle.com \
    --cc=stephenn@xilinx.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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