From: Steven Cole <elenstev@mesatop.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Dax Kelson <dax@gurulabs.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: List of SCO files
Date: Wed, 12 Nov 2003 21:50:43 -0700 [thread overview]
Message-ID: <200311122150.43307.elenstev@mesatop.com> (raw)
In-Reply-To: <1068691791.13135.41.camel@gaston>
On Wednesday 12 November 2003 07:49 pm, Benjamin Herrenschmidt wrote:
> Or just include/asm-m68k/spinlock.h :)
>
> The whole file is just:
>
> #ifndef __M68K_SPINLOCK_H
> #define __M68K_SPINLOCK_H
>
> #error "m68k doesn't do SMP yet"
>
> #endif
Here's my personal favorite, file 490 of 591.
See if you can spot the purloined Intellectual Property:
[steven@spc 2.6-bk-current]$ cat include/asm-v850/percpu.h
#ifndef __V850_PERCPU_H__
#define __V850_PERCPU_H__
#include <asm-generic/percpu.h>
/* This is a stupid hack to satisfy some grotty implicit include-file
dependency; basically, <linux/smp.h> uses BUG_ON, which calls BUG, but
doesn't include the necessary headers to define it. In the twisted
festering mess of includes this must all be resolved somehow on other
platforms, but I haven't the faintest idea how, and don't care; here will
do, even though doesn't actually make any sense. */
#include <asm/page.h>
#endif /* __V850_PERCPU_H__ */
I'm betting on the "This is a stupid hack" phrase. Undoubtably SCO's code
is littered with comments like that.
Steven
next prev parent reply other threads:[~2003-11-13 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 23:32 Dax Kelson
2003-11-13 2:49 ` Benjamin Herrenschmidt
2003-11-13 4:50 ` Steven Cole [this message]
2003-11-14 9:35 ` Jon Evans
2003-11-13 9:36 ` Geert Uytterhoeven
2003-11-13 15:19 ` Jes Sorensen
2003-11-13 15:26 ` Richard B. Johnson
2003-11-13 12:57 ` Rik van Riel
2003-11-16 16:03 ` Dick Streefland
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=200311122150.43307.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=benh@kernel.crashing.org \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome