All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Florian Schirmer" <jolt@tuxbox.org>
To: "David Woodhouse" <dwmw2@infradead.org>,
	"Andre Hedrick" <andre@linux-ide.org>
Cc: <linux-kernel@vger.kernel.org>, "David Turner" <novalis@fsf.org>,
	<andrew@mikl.as>, <rob@nocat.net>
Subject: Re: Linksys/Cisco GPL Violations
Date: Mon, 13 Oct 2003 11:40:30 +0200	[thread overview]
Message-ID: <004a01c3916e$0b736d90$9602010a@jingle> (raw)
In-Reply-To: 1065854106.30987.394.camel@imladris.demon.co.uk

Hi,

i'm very sorry but i've to bring this topic to your attention again. We've
the source now. Fine. But there is no single sign of a GPL (compatible)
license anywhere. There are some "Broadcom All rights reserved" copyrights.
So i'm wondering wether the files inherit the GPL or do they have to be
declared as GPL by Broadcom? The license of the other files (non linux
kernel related) is somewhat unclear too.

Thanks for sharing your opinions.

Regards,
    Florian


  parent reply	other threads:[~2003-10-13  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 18:22 Linksys/Cisco GPL Violations David Turner
2003-10-06  8:29 ` David Woodhouse
2003-10-10 13:09   ` Florian Schirmer
2003-10-10 13:16     ` David Woodhouse
2003-10-10 13:26       ` Florian Schirmer
2003-10-10 13:39         ` David Woodhouse
2003-10-10 14:18           ` Florian Schirmer
2003-10-10 14:25             ` David Woodhouse
2003-10-11  5:37               ` Andre Hedrick
2003-10-11  6:35                 ` David Woodhouse
2003-10-11  7:03                   ` Andre Hedrick
2003-10-13  9:40                   ` Florian Schirmer [this message]
2003-10-10 15:11     ` [Linux-bcom4301-priv] " James Stevenson
2003-10-10 15:29       ` Sasa Ostrouska
2003-10-10 16:36         ` Florian Schirmer
2003-10-10 16:58           ` Luite Stegeman
2003-10-10 15:58     ` Rob Flickenger

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='004a01c3916e$0b736d90$9602010a@jingle' \
    --to=jolt@tuxbox.org \
    --cc=andre@linux-ide.org \
    --cc=andrew@mikl.as \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=novalis@fsf.org \
    --cc=rob@nocat.net \
    /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.