mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Adrian Bunk <bunk@kernel.org>,
	grundler@parisc-linux.org, kyle@mcmartin.ca, matthew@wil.cx,
	linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, bdale@hp.com
Subject: Re: [2.6 patch] binfmt_som.c: add MODULE_LICENSE
Date: Fri, 15 Aug 2008 15:44:34 -0600	[thread overview]
Message-ID: <20080815214434.GB5773@colo.lackof.org> (raw)
In-Reply-To: <20080811145652.100E74E77@hiauly1.hia.nrc.ca>

On Mon, Aug 11, 2008 at 10:56:51AM -0400, John David Anglin wrote:
...
> I don't understand why we are talking about HP here.

My bad. I thought HP owned the copy right to the bulk of the code
and Matthew demonstrated they do not.

>  According to
> Matthew, his last commit to this file occured while he worked for
> Genedata.  It is my understanding that copyright normally acrues
> to employers in employment situations.  If Matthew was an employee
> and not an independent contractor at the time, then why are we not
> talking about Genedata, or its subsequent owner?  Subsequent
> employment at HP or their funding of the parisc port shouldn't
> affect the licensing of a file that was previously contributed.

Correct. I thought the work was done by HP employees and that was wrong.

sorry,
grant

> The file appears to be a derived work.  This may also affect its
> copyright status.  The only reason HP should be involved is if the
> file somehow contains material copyrighted by HP.
> 
> The whole licensing issue for the linux program and modules,
> particularly for individual files, appears to be a mess.  The
> COPYING file is vague on the licensing for files.   The recommended
> wording suggested by the FSF isn't used.  I can't see that adding
> MODULE_LICENSE("GPL") lines is going to help much.
> 
> There are several GPL licenses and versions.  The line isn't
> going to mean much to a lawyer.  I really think each file should
> be specific about its licensing in words that can be clearly
> understood.
> 
> Dave
> -- 
> J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
> National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

  parent reply	other threads:[~2008-08-15 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 21:11 Adrian Bunk
2008-08-10  0:55 ` Grant Grundler
2008-08-10  1:00   ` Matthew Wilcox
2008-08-10 13:41     ` Bdale Garbee
2008-08-10 15:14       ` Matthew Wilcox
2008-08-11  0:05         ` Grant Grundler
2008-08-11 14:15         ` Bdale Garbee
2008-08-10 14:11   ` Adrian Bunk
2008-08-11  0:10     ` Grant Grundler
2008-08-11 10:46       ` Adrian Bunk
2008-08-11 14:56         ` John David Anglin
2008-08-11 15:51           ` Adrian Bunk
2008-08-11 16:56             ` John David Anglin
2008-08-11 18:43               ` Adrian Bunk
2008-08-11 17:11           ` Matthew Wilcox
2008-08-15 21:44           ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-15 16:13 Adrian Bunk

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=20080815214434.GB5773@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=akpm@linux-foundation.org \
    --cc=bdale@hp.com \
    --cc=bunk@kernel.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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

Powered by JetHome