All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Qualcomm "All Rights Reserved" in Linux staging
Date: Fri, 4 Jul 2014 15:12:05 -0700	[thread overview]
Message-ID: <20140704221205.GA32013@kroah.com> (raw)
In-Reply-To: <1404511548.18844.3.camel@x220>

On Sat, Jul 05, 2014 at 12:05:48AM +0200, Paul Bolle wrote:
> On Fri, 2014-07-04 at 21:20 +0000, Mathieu Desnoyers wrote:
> > 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.
> 
> That's actually a common pattern:
>     $ git grep -i "Copyright.*All Rights Reserved" v3.16-rc3 | wc -l
>     5203

Yeah, I used to be "worried" about that as well, turns out it means
nothing :)

It's the license of the code that is the issue, not the copyright line,
which all lawyers tell me now shouldn't even be in a file, as it, again,
means nothing.

thanks,

greg k-h

  reply	other threads:[~2014-07-04 22:12 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 ` Qualcomm "All Rights Reserved" in Linux staging Mathieu Desnoyers
2014-07-04 22:05   ` Paul Bolle
2014-07-04 22:12     ` gregkh [this message]
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=20140704221205.GA32013@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=pebolle@tiscali.nl \
    /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.