public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Copyright/License text in cpu/ppc4xx/4xx_pci.c
Date: Wed, 8 Jul 2009 20:24:36 +0200	[thread overview]
Message-ID: <200907082024.37153.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20090708155143.D7188832E416@gemini.denx.de>

Hi,

> Dear Matthias Fuchs,
> 
> In message <200907081621.51898.matthias.fuchs@esd.eu> you wrote:
> >
> > > On Wednesday 08 July 2009 15:40:08 Matthias Fuchs wrote:
> > > > I am just cleaning up cpu/ppc4xx/4xx_pci.c (mainly coding style stuff).
> > > > I am wondering about the file's header. I think even when this code comes
> > > > initially from IBM there is not much left from original IBM code.
> > > 
> > > Yes, this could be the case.
> > > 
> > > > So can we replace the header with the widely used GPL template?
> > > 
> > > I'm not sure here. The paragraph clearly states:
> > > 
> > >  *       Any person who transfers this source code or any derivative work
> > >  *       must include the IBM copyright notice, this paragraph, and the
> > >  *       preceding two paragraphs in the transferred software.
> > > 
> > > So even if the current version has not much in common with the original 
> > > version (IIRC cloned from IBM PIBS), we still have to carry it with us. At 
> > > least this is how I interpret it.
> > But we could prepend the typical header which brings us to something like this:
> 
> You could do it, but you  are  eventually  not  permitted  to  do  it
> legally.
> 
> The fact that you "must include the IBM copyright notice, this
> paragraph, and the preceding two paragraphs in the transferred
> software" may or may not be compatible with GPL - IANAL...

Same with me. I cannot understand how maybe-GPL-incompatable 
sources can be part of U-Boot. This file is not the only one.
Also the top level README says that the sources are under the GPL.
So does it even play any role when the GPL lines are not contained in some files?
Isn't it enough to have the licence of the whole project mentioned once?

To be on the legal side, I will keep the GPL note off this file.
Same with me. IANAL. And I am not very motivated to become one sooner or later.

Matthias

  parent reply	other threads:[~2009-07-08 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 13:40 [U-Boot] Copyright/License text in cpu/ppc4xx/4xx_pci.c Matthias Fuchs
2009-07-08 13:57 ` Stefan Roese
2009-07-08 14:21   ` Matthias Fuchs
2009-07-08 14:31     ` Stefan Roese
2009-07-08 15:51     ` Wolfgang Denk
2009-07-08 17:50       ` Robin Getz
2009-07-08 18:24       ` Matthias Fuchs [this message]
2009-07-08 19:03         ` Wolfgang Denk
2009-07-08 20:51           ` Matthias Fuchs
2009-07-08 20:57             ` Wolfgang Denk
2009-07-09  8:44               ` Matthias Fuchs
2009-07-09  9:00                 ` Stefan Roese
2009-07-09  9:24                   ` Matthias Fuchs
2009-07-09  9:51                     ` Stefan Roese
2009-07-09 10:10                       ` Wolfgang Denk
2009-07-09 10:15                         ` Stefan Roese
2009-07-09 12:20                           ` Wolfgang Denk
2009-07-09 12:23                             ` Stefan Roese
2009-07-21 11:42                       ` Matthias Fuchs
2009-07-21 11:58                         ` Stefan Roese
2009-07-21 14:09                         ` Scott McNutt

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=200907082024.37153.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.com \
    --cc=u-boot@lists.denx.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