All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [OT] use of patented algorithms in the kernel ok or not?
Date: Sun, 21 Dec 2003 08:35:09 -0500 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.44.0312210833030.3044-100000@thoron.boston.redhat.com> (raw)
In-Reply-To: <20031221105333.GC3438@mail.shareable.org>

On Sun, 21 Dec 2003, Jamie Lokier wrote:

> Albert Cahalan wrote:
> > What about the obvious Kconfig option?
> > 
> > config PATENT_1234567890
> >         bool "Patent 1234567890"
> >         default n
> >         help
> >           Say Y here if you have the right to use
> >           patent 1234567890 (the foo patent). Some
> >           countries do not recognise this patent, an
> >           educational or research exemption may apply,
> >           you may be the patent holder, the patent
> >           may have expired, or you may have aquired
> >           rights via licensing. Seek legal help if you
> >           need advice concerning your rights. If unsure,
> >           say N.
> 
> I expect this was said in jest, but it would be delightful to see this
> done for real.  To the best of my knowlege it's uncharted territory,
> so perhaps what you suggest _would_ be upheld in a court of law as
> permissible?
> 

This approach would turn Linux into proprietary software.


- James
-- 
James Morris
<jmorris@redhat.com>



  reply	other threads:[~2003-12-21 13:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21  1:12 [OT] use of patented algorithms in the kernel ok or not? Albert Cahalan
2003-12-21 10:53 ` Jamie Lokier
2003-12-21 13:35   ` James Morris [this message]
2003-12-21 14:30     ` Jamie Lokier
2003-12-21 16:03       ` Xavier Bestel
2003-12-21 14:56     ` Arjan van de Ven
2003-12-21 19:33       ` Stan Bubrouski
2003-12-21 23:25         ` Helge Hafting
2003-12-21 19:29   ` Stan Bubrouski
2003-12-21 19:55     ` Matthias Schniedermeyer
2003-12-21 20:11       ` Stan Bubrouski
2003-12-21 21:52       ` Francois Romieu
2003-12-21 21:57     ` Jamie Lokier
2003-12-22  9:50       ` John Bradford
2003-12-22 15:34         ` Adrian Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-12-22  1:43 James Lamanna
2003-12-22 11:32 ` Matti Aarnio
2003-12-18 23:11 Lennert Buytenhek
2003-12-19  6:10 ` Linus Torvalds
2003-12-19  7:38 ` Paul Jackson
2003-12-19  8:47 ` Arjan van de Ven
2003-12-19 11:38   ` Jan-Benedict Glaw
2003-12-20 17:28   ` Stefan Traby
2003-12-21 10:33   ` Jamie Lokier
2003-12-21 16:57     ` Pavel Machek
2004-01-13 15:35       ` Chuck Campbell
2004-01-13 19:35         ` Pavel Machek
2004-01-13 21:04           ` Richard B. Johnson
2003-12-22  0:37     ` jw schultz
2003-12-21 23:39   ` Lennert Buytenhek
2003-12-21  1:25 ` jw schultz
2003-12-21 19:40   ` Lennert Buytenhek

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=Xine.LNX.4.44.0312210833030.3044-100000@thoron.boston.redhat.com \
    --to=jmorris@redhat.com \
    --cc=albert@users.sourceforge.net \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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.