public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: gregkh <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Qualcomm "All Rights Reserved" in Linux staging
Date: Fri, 4 Jul 2014 21:20:28 +0000 (UTC)	[thread overview]
Message-ID: <1983136768.8892.1404508828693.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1086604719.8856.1404508237223.JavaMail.zimbra@efficios.com>

Hi Greg,

Reading this story about Qualcomm lawyers shooting
DMCA takedown requests lightly against github projects:

http://linux.slashdot.org/story/14/07/04/1455200/qualcomm-takes-down-100-github-repositories-with-dmca-notice
http://www.phoronix.com/scan.php?page=news_item&px=MTczNDU
https://github.com/github/dmca/blob/master/2014-07-02-Qualcomm.md

It appears to me that the mere presence of those lines
in Linux staging:

grep -r "Qualcomm" . |grep -i "rights"
./drivers/staging/ft1000/ft1000-usb/ft1000_usb.c: * CopyRight (C) 2007 Qualcomm Inc. All Rights Reserved.
./drivers/staging/ft1000/ft1000-usb/ft1000_download.c:* CopyRight (C) 2007 Qualcomm Inc. All Rights Reserved.
./drivers/staging/ft1000/ft1000-usb/ft1000_hw.c:/* CopyRight (C) 2007 Qualcomm Inc. All Rights Reserved.

might be contradicting the Dual MPL/GPL license
expressed by MODULE_LICENSE() for those files.
Perhaps we should ask some clarification on
licensing of those files to Qualcomm ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

       reply	other threads:[~2014-07-04 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1086604719.8856.1404508237223.JavaMail.zimbra@efficios.com>
2014-07-04 21:20 ` Mathieu Desnoyers [this message]
2014-07-04 22:05   ` Qualcomm "All Rights Reserved" in Linux staging Paul Bolle
2014-07-04 22:12     ` gregkh
2014-07-07 13:03   ` One Thousand Gnomes

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=1983136768.8892.1404508828693.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=gregkh@linuxfoundation.org \
    --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