From: Brad Boyer <flar@allandria.com>
To: Greg KH <greg@kroah.com>
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org,
zippel@linux-m68k.org, torvalds@osdl.org,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: License oddity in some m68k files
Date: Thu, 19 Jan 2006 11:05:17 -0800 [thread overview]
Message-ID: <20060119190517.GA4472@pants.nu> (raw)
In-Reply-To: <20060119180947.GA25001@kroah.com>
On Thu, Jan 19, 2006 at 10:09:47AM -0800, Greg KH wrote:
> Any ideas of how they made it into our tree? And any chance of
> correcting them to be the correct license or removing them?
This is pretty old stuff. The files in arch/m68k/fpsp040/
implement all the extra 68881/68882 instructions that they
left out of the FPU that is builtin on the 68040. This is
the official Motorola provided implementation of them, and
they seem to be widely available. I have no idea on the
license issues, however. One thing to note is that there is
a README file in that directory that appears to be part of
the original distribution of this code from Motorola with
some license info.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2006-01-19 19:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 18:09 License oddity in some m68k files Greg KH
2006-01-19 19:05 ` Brad Boyer [this message]
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=20060119190517.GA4472@pants.nu \
--to=flar@allandria.com \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--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