linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Larry McVoy <lm@bitmover.com>
Cc: akuster@mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: GPL inconsistency in arch/ppc/ocp/xlinx/
Date: Sun, 15 Jun 2003 19:39:15 +0200	[thread overview]
Message-ID: <20030615173915.GA4511@lst.de> (raw)
In-Reply-To: <20030612204444.GA19453@work.bitmover.com>


On Thu, Jun 12, 2003 at 01:44:44PM -0700, Larry McVoy wrote:
> You might want to be careful about advertising why you want these files
> removed because the Xilinx clause is just covering their butt.  If someone
> uses Linux in some life support system and someone dies, the fact that
> the community removed these files because of that clause could be construed
> as a statement that Linux was suitable for life support systems.  It gives
> the lawyers ammo.

The issue is not what you, I or Xilinx think is a good idea to do with
the code, the issue is that the GPL doesn't allow to further restrict
the rights it gives.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-06-15 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 20:12 GPL inconsistency in arch/ppc/ocp/xlinx/ Christoph Hellwig
2003-05-25 12:01 ` Paul Mackerras
2003-06-12 20:32 ` Christoph Hellwig
2003-06-12 20:44   ` Larry McVoy
2003-06-13  7:58     ` Giuliano Pochini
2003-06-15 17:39     ` Christoph Hellwig [this message]
2003-06-12 20:45   ` Matt Porter
2003-06-15 17:41     ` Christoph Hellwig
2003-06-16  0:07       ` Tom Rini
2003-06-12 20:55   ` Tom Rini
2003-06-15 17:47     ` Christoph Hellwig
2003-06-16  0:04       ` Tom Rini
2003-06-17  4:50     ` Peter Ryser

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=20030615173915.GA4511@lst.de \
    --to=hch@lst.de \
    --cc=akuster@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=lm@bitmover.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;
as well as URLs for NNTP newsgroup(s).