From: Hans Reiser <reiser@namesys.com>
To: Stefan Traby <stefan@hello-penguin.com>
Cc: Jason Holt <jason@lunkwill.org>, reiserfs-list@namesys.com
Subject: Re: reiserfs_fs.h listed in SCO court docs
Date: Wed, 12 Nov 2003 08:44:31 -0800 [thread overview]
Message-ID: <3FB2636F.8030905@namesys.com> (raw)
In-Reply-To: <20031113004312.GA17130@hello-penguin.com>
Stefan Traby wrote:
>On Wed, Nov 12, 2003 at 04:23:46AM -0800, Hans Reiser wrote:
>
>
>
>>>http://www.groklaw.net/article.php?story=2003111203544653
>>>
>>>And they list:
>>>
>>>fs/reiserfs/do_balan.c
>>>fs/reiserfs/fix_node.c
>>>include/linux/reiserfs_fs.h
>>>
>>>Hans, did you sneaky look through SCO's IP and use it when writing your
>>>code?
>>>
>>>
>
>
>
>>Hunh?
>>
>>Do they claim that we call some function that infringes (I have no idea
>>what, kmalloc or something....) or that our code in that file itself
>>infringes? When someone doesn't tell you what is allegedly infringing
>>it is reallly hard to do anything.
>>
>>
>
>asp:~/linux/fs/reiserfs# grep \ SMP *.c
>do_balan.c: using buffers already obtained. For SMP support it will someday be
>fix_node.c: * When ported to SMP kernels, only at the last moment after all needed nodes
>asp:~/linux/fs/reiserfs#
>
>
>SCO really sucks.
>There was simply no real investigation.
>
>
>
You are absolutely right. You forgot the includes....
reiser@bitspit:/usr/src/linux/include/linux> grep SMP reiserfs_fs*
reiserfs_fs.h:gods only know how we are going to SMP the code that uses
them.
Oh would I like to make a court appearance regarding this one....
--
Hans
next prev parent reply other threads:[~2003-11-12 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 23:14 reiserfs_fs.h listed in SCO court docs Jason Holt
2003-11-12 12:23 ` Hans Reiser
2003-11-13 0:43 ` Stefan Traby
2003-11-12 16:44 ` Hans Reiser [this message]
2003-11-13 0:43 ` Andreas Dilger
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=3FB2636F.8030905@namesys.com \
--to=reiser@namesys.com \
--cc=jason@lunkwill.org \
--cc=reiserfs-list@namesys.com \
--cc=stefan@hello-penguin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.