From: Greg KH <greg@kroah.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org, zippel@linux-m68k.org
Cc: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: License oddity in some m68k files
Date: Thu, 19 Jan 2006 10:09:47 -0800 [thread overview]
Message-ID: <20060119180947.GA25001@kroah.com> (raw)
Someone recently pointed out to me the following wording on some of the
m68k files that reads:
| Copyright (C) Motorola, Inc. 1990
| All Rights Reserved
|
| THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF MOTOROLA
| The copyright notice above does not evidence any
| actual or intended publication of such source code.
This shows up in the following files:
arch/m68k/fpsp040/bindec.S
arch/m68k/fpsp040/binstr.S
arch/m68k/fpsp040/bugfix.S
arch/m68k/fpsp040/decbin.S
arch/m68k/fpsp040/do_func.S
arch/m68k/fpsp040/fpsp.h
arch/m68k/fpsp040/gen_except.S
arch/m68k/fpsp040/get_op.S
arch/m68k/fpsp040/kernel_ex.S
and seems to predate the bitkeeper tree, so it's a bit hard to figure
out where they came from.
Any ideas of how they made it into our tree? And any chance of
correcting them to be the correct license or removing them?
thanks,
greg k-h
next reply other threads:[~2006-01-19 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 18:09 Greg KH [this message]
2006-01-19 19:05 ` License oddity in some m68k files Brad Boyer
2006-01-19 20:14 ` Roman Zippel
2006-01-19 22:04 ` Greg KH
2006-01-19 22:14 ` Alan Cox
2006-01-19 22:32 ` Greg KH
2006-01-20 12:21 ` Ric Wheeler
2006-01-20 12:34 ` Alan Cox
2006-01-20 13:45 ` Ric Wheeler
2006-01-20 14:49 ` Kumar Gala
2006-01-19 21:40 ` Alan Cox
2006-01-20 7:52 ` Jes Sorensen
2006-01-20 8:52 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 0:24 Matt Waddel
2006-01-21 0:36 ` Greg KH
2006-01-30 18:03 ` Alan Cox
2006-02-01 4:02 ` Matt Waddel
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=20060119180947.GA25001@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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