From: Rogelio Serrano <rogelio.serrano@gmail.com>
To: "luke.leighton" <luke.leighton@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Transcend's "one of the most cavalier GPL violations in a long time"
Date: Tue, 8 Oct 2013 17:08:22 +0100 [thread overview]
Message-ID: <CANszf4iyed-tCBK7g8HEWgBpTXydSwcsRTA1UzyxZhN1uy0vQg@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDyaEo-7NzEYfxU7Hofq08Raepc_JFevoqF+Nzrwzz2kXQ@mail.gmail.com>
On Fri, Sep 20, 2013 at 12:29 PM, luke.leighton <luke.leighton@gmail.com> wrote:
> this is a quick message to let people know that evidence has been
> collected of not just knowingly-infringing copyright but *blatant*
> copyright infringment [a la "bring it on, fuckers"] by transcend
> technologies. does anyone have any recommendations as to whom should
> be contacted in order to pursue a copyright violation case against
> transcend? as a minor linux kernel source copyright holder they could
> easily and simply remove the source code contributions i have made,
> but i would still like to pursue them for copyright infringment.
>
>
I dont think the majority of linux kernel developers care about
enforcement at all. Its virtually public domain as far as i can see,
Linus himself will not run after violators.
Any company out there is free to do what they want.
> ---------- Forwarded message ----------
> From: luke.leighton <luke.leighton@gmail.com>
> Date: Fri, Sep 20, 2013 at 12:25 PM
> Subject: Re: Transcend's "one of the most cavalier GPL violations in a
> long time"
> To: Fernando Cassia <fcassia@gmail.com>
> Cc: legal <legal@lists.gpl-violations.org>
>
>
> On Fri, Sep 20, 2013 at 6:36 AM, Fernando Cassia <fcassia@gmail.com> wrote:
>> Sorry if this has been already discussed on this list...
>>
>> http://hackaday.com/2013/09/19/advanced-transcend-wifi-sd-hacking-custom-kernels-x-and-firefox/
>>
>> "After all this was done, [Dmitry] finally got a response back from
>> one of Transcend’s support engineers. They are “Uninterested” in
>> complying with GPL, and he is “free to report this to any Linux
>> organization” Ouch! That’s one of the most cavalier GPL violations
>> we’ve seen in a long time."
>
> not only that but it would provide the courts with clear evidence of
> blatant copyright infringment. the penalties for such are extremely
> high.
>
> l.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-10-08 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACGw4H5+5bkgy+UJPCbwG2KXZDj3zhXLR4cZCbeDvjJhfTJwmQ@mail.gmail.com>
[not found] ` <CAPweEDzf1DbRHeXr_cL8ZZk9s0Srhp0s5rrYm0pksyurO0CXpw@mail.gmail.com>
2013-09-20 11:29 ` Fwd: Transcend's "one of the most cavalier GPL violations in a long time" luke.leighton
2013-10-08 14:47 ` Pavel Machek
2013-10-08 16:08 ` Rogelio Serrano [this message]
2013-10-13 12:02 ` Pavel Machek
2013-10-15 6:42 ` Rogelio Serrano
2013-10-15 7:48 ` Mats Liljegren
2013-10-15 11:10 ` Pavel Machek
2013-10-28 0:28 ` Rob Landley
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=CANszf4iyed-tCBK7g8HEWgBpTXydSwcsRTA1UzyxZhN1uy0vQg@mail.gmail.com \
--to=rogelio.serrano@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.leighton@gmail.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).