public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mdpoole@troilus.org
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: greg@kroah.com, hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Fri, 18 Jun 2004 07:09:57 -0400	[thread overview]
Message-ID: <87k6y5w29m.fsf@sanosuke.troilus.org> (raw)
In-Reply-To: <200406180656.i5I6udn14886@adam.yggdrasil.com> (Adam J. Richter's message of "Thu, 17 Jun 2004 23:56:39 -0700")

Adam J. Richter writes:

> On Thu, Jun 17, 2004 at 04:22:42PM -0400, mdpoole@troilus.org wrote:
>> http://www.ipwatchdog.com/equitable_estoppel.html discusses equitable
>> estoppel vis-a-vis patent rights (which are treated similarly to
>> copyrights by many courts).  When you contributed your changes to the
>> USB maintainers, they -- and later redistributors -- inferred that you
>> would not allege copyright infringement by applying your changes to
>> the kernel that existed then.
>
> 	From my reading of that web page, it does not seem to me
> that one would have a case of either equitable estoppel or implied
> license (for example, "silence alone is generally not sufficient
> affirmative conduct to give rise to estoppel").  I've made my
> opposition to the illegal drivers clear from the time that I've
> been aware of them.

Really?  I see that one of the previous authors listed on your
copyright filing is Hugh Blemings, listed as "author of keyspan
support for Linux."  I will repeat my question: Did you really do
copyrightable work on the USB serial drivers yet somehow fail to
notice the many firmware header files already there?

> 	If you are not fabricating claims about inferences
> by "the USB maintainers [...] and later distributors", I would
> be interested in your citing some historical examples of the
> "USB mainatiners" stating this inference and not being corrected.

They need not have stated it explicitly; they just have to have relied
on it.  People who are sent patches by the patch's author infer by
that submission that including the patch(es) will not lead to claims
of copyright infringement by that author.  This is common sense.  If
you have any example where someone rejected a patch from the patch's
author out of concern for copyright infringement claims by that
author, I'd like to see it.

There was recent in-depth discussion on debian-legal about further
reasons that would bar your claim of copyright infringement.  Since
you declined to answer all of what I wrote before, I will not bore you
by repeating those arguments here.

Michael

  reply	other threads:[~2004-06-18 11:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  6:56 more files with licenses that aren't GPL-compatible Adam J. Richter
2004-06-18 11:09 ` mdpoole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-18  6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09   ` Adam J. Richter
2004-06-17 19:14     ` Kyle Moffett
2004-06-17 20:51       ` Flavio Stanchina
2004-06-17 20:53         ` Kyle Moffett
2004-06-17 21:05         ` mdpoole
2004-06-17 21:10           ` Christoph Hellwig
2004-06-17 21:45           ` Flavio Stanchina
2004-06-17 20:22     ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54   ` Christoph Hellwig
2004-06-17 20:22     ` Greg KH
2004-06-17 20:30       ` Christoph Hellwig
2004-06-17 20:52         ` Greg KH
2004-06-16 23:47 Wichmann, Mats D
2004-06-17  1:18 ` Kyle Moffett
2004-06-15 20:57 Christoph Hellwig
2004-06-16  0:38 ` Eric
2004-06-16  1:27   ` Kyle Moffett
2004-06-16  4:11   ` David Schwartz
2004-06-16 20:34     ` Erik Harrison
2004-06-16 20:37       ` Christoph Hellwig
2004-06-16 21:21       ` David Schwartz
2004-06-16 22:45         ` Oliver Neukum
2004-06-16 23:45           ` David Schwartz
2004-06-17 14:09             ` Timothy Miller
2004-06-17 18:35               ` David Schwartz
2004-06-17 19:22                 ` Timothy Miller
2004-06-17  7:59           ` Christoph Hellwig
2004-06-17  8:43             ` Oliver Neukum
2004-06-17  8:47               ` Christoph Hellwig
2004-06-17 10:09             ` Martin Diehl
2004-06-17 10:14               ` Christoph Hellwig
2004-06-19 18:29               ` David Woodhouse
2004-06-17 14:04           ` Timothy Miller
2004-06-16 22:49       ` Helge Hafting
2004-06-18  9:08         ` Adrian Cox
2004-06-18 11:21           ` Kyle Moffett

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=87k6y5w29m.fsf@sanosuke.troilus.org \
    --to=mdpoole@troilus.org \
    --cc=adam@yggdrasil.com \
    --cc=greg@kroah.com \
    --cc=hch@lst.de \
    --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