public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: stan.cunningham@yahoo.com
Cc: Chris Snook <csnook@redhat.com>,
	linux-kernel@vger.kernel.org, legal@narasimha.gpl-violations.org,
	license-violation@gnu.org
Subject: Re: ASUS SplashTop and Phoenix Hyperspace infringing kernel copyright and GPL
Date: Thu, 05 Jun 2008 12:25:19 +0930	[thread overview]
Message-ID: <48475597.2010108@davidnewall.com> (raw)
In-Reply-To: <98404.93587.qm@web57413.mail.re1.yahoo.com>

Stan Cunningham wrote:
> There are several unresolved issues: first of all, it is ASUS and not DeviceVM that is distributing the binary to customers who buy motherboards and laptops.

Yet it is DeviceVM that distributes it to ASUS, so the GPL obligations
attach thereto.

  reply	other threads:[~2008-06-05  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 22:39 ASUS SplashTop and Phoenix Hyperspace infringing kernel copyright and GPL Stan Cunningham
2008-05-19 22:57 ` Chris Snook
2008-06-04 23:31   ` Stan Cunningham
2008-06-05  2:55     ` David Newall [this message]
2008-06-05  8:54     ` Alan Cox

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=48475597.2010108@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=csnook@redhat.com \
    --cc=legal@narasimha.gpl-violations.org \
    --cc=license-violation@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stan.cunningham@yahoo.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