LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Farnsworth <dale@farnsworth.org>
To: John.Linn@xilinx.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Xilinx : Framebuffer Driver: Add PLB support (non-DCR)
Date: Thu, 09 Apr 2009 08:36:11 -0700	[thread overview]
Message-ID: <E1LrwIV-0008UK-BS@xyzzy.farnsworth.org> (raw)
In-Reply-To: <20090409141651.72775AC0056@mail192-sin.bigfish.com>

> > -----Original Message-----
> > From: Stephen Rothwell [mailto:sfr@canb.auug.org.au] 
> > Sent: Wednesday, April 08, 2009 7:52 PM
> > To: John Linn
> > Cc: grant.likely@secretlab.ca; jwboyer@linux.vnet.ibm.com; 
> > linuxppc-dev@ozlabs.org; 
> > linux-fbdev-devel@lists.sourceforge.net; 
> > akonovalov@ru.mvista.com; adaplas@gmail.com; Suneel Garapati; Suneel
> > Subject: Re: [PATCH] Xilinx : Framebuffer Driver: Add PLB 
> > support (non-DCR)
> > 
> > Hi John,
> > 
> > On Wed, 8 Apr 2009 15:11:25 -0600 John Linn 
> > <john.linn@xilinx.com> wrote:
> > >
> > >   * 2002-2007 (c) MontaVista Software, Inc.
> > >   * 2007 (c) Secret Lab Technologies, Ltd.
> > > + * 2009 (c) Xilinx Inc.
> > >   *
> > > - * This file is licensed under the terms of the GNU 
> > General Public License
> > > - * version 2.  This program is licensed "as is" without 
> > any warranty of any
> > > - * kind, whether express or implied.
> > > + * 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.
> > > + *
> > > + * 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.
> > 
> > This changes the license for this file (from "GPLv2" to "GPLv2 or
> > later").  Have you asked the other copyright owners about that?
> 
> Andrei was copied on the patch, we'll see if he has any thoughts about
> it. 

Although I work for MontaVista, I don't speak for them on licensing issues.

In my opinion, unless someone can come up with a compelling reason
for changing the license terms of a file, they shouldn't be changed.
MontaVista made a deliberate, considered decision to license that file
under GPLv2 and not "GPLv2 or later".  Those who use and distribute
modifications to GPLv2 licensed work need to respect the license.

-Dale

  parent reply	other threads:[~2009-04-09 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 21:11 [PATCH] Xilinx : Framebuffer Driver: Add PLB support (non-DCR) John Linn
2009-04-09  1:51 ` Stephen Rothwell
2009-04-09 14:16   ` John Linn
2009-04-09 14:30     ` Grant Likely
2009-04-09 15:36     ` Dale Farnsworth [this message]
2009-04-09 15:38       ` John Linn
2009-04-09 12:46 ` Josh Boyer
2009-04-09 14:06   ` Roderick Colenbrander
2009-04-09 14:33     ` Josh Boyer
2009-04-09 14:34     ` Grant Likely
2009-04-09 14:36       ` John Linn
2009-04-09 14:34   ` John Linn
2009-04-09 14:41   ` John Linn

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=E1LrwIV-0008UK-BS@xyzzy.farnsworth.org \
    --to=dale@farnsworth.org \
    --cc=John.Linn@xilinx.com \
    --cc=linuxppc-dev@ozlabs.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