From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: jonathan@jonmasters.org
Cc: Christoph Hellwig <hch@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Robert Love <rml@novell.com>,
Ankit Jain <ankitjain1580@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Wed, 29 Sep 2004 14:03:54 -0600 [thread overview]
Message-ID: <415B152A.2010008@drdos.com> (raw)
In-Reply-To: <35fb2e590409291328458ebebd@mail.gmail.com>
Jon Masters wrote:
>On Wed, 29 Sep 2004 13:43:32 -0600, Jeff V. Merkey <jmerkey@drdos.com> wrote:
>
>
>
>>Since they are hiring as many top Linux folks as possible, and they have
>>invested their entire future in Linux, I think their actions speak so loud,
>>
>>
>
>I only asked because I'd not heard of an official patent position from
>them (but I've not looked) and I wondered if someone happened to know
>- words are completely meaningless.
>
><snip>
>
>Wow, tha'ts one bitter mail you sent. Sorry to hear about it but I'd
>rather not start a general discussion about big business practices and
>Novell - just interested in the patent situation.
>
>Jon.
>
>
>
Just letting you have a little insight into what their position might
be. It's not bitter, it's
factual, and I got over Novell a long time ago. They will probably
ignore you for now, but
in the future, if Linux contains IP from sources they consider theirs,
it would be possible
for them to shut out competitors without a license from them. Not only
on this topic, but
any other area their employees have contributed for which they hold
patents. This case may
be a special one, but anytime you use patented materials are even areas
where there is a doubt
there is exposure. I have a release from them and I can use any IP I
retained in a non-tangible
form that would have been theirs. So I can use this patent without
concern of infringement
claims. But since I did not instrument the affinity code in Linux, it's
not protected this way.
NWFS is protected this way and people can use it without fear of claims
from Novell.
Jeff
next prev parent reply other threads:[~2004-09-29 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:25 processor affinity Ankit Jain
2004-09-28 13:39 ` Toon van der Pas
2004-09-28 13:47 ` Jon Masters
2004-09-28 13:55 ` Neil Horman
2004-09-28 14:04 ` Jeff V. Merkey
2004-09-28 15:58 ` Robert Love
2004-09-28 16:02 ` Jeff V. Merkey
2004-09-28 21:51 ` Alan Cox
2004-09-29 16:56 ` Jeff V. Merkey
2004-09-29 17:45 ` Christoph Hellwig
2004-09-29 19:24 ` Jeff V. Merkey
2004-09-29 20:08 ` Jon Masters
2004-09-29 19:43 ` Jeff V. Merkey
2004-09-29 20:28 ` Jon Masters
2004-09-29 20:03 ` Jeff V. Merkey [this message]
2004-09-30 2:39 ` Nick Piggin
[not found] ` <20040930124708.GA2520@galt.devicelogics.com>
2004-10-01 3:09 ` Nick Piggin
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=415B152A.2010008@drdos.com \
--to=jmerkey@drdos.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ankitjain1580@yahoo.com \
--cc=hch@infradead.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox