All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Thu, 11 Jun 2015 17:52:00 -0700	[thread overview]
Message-ID: <20150612005200.GB26737@kroah.com> (raw)
In-Reply-To: <20150611232623.GA2026@www.mrbrklyn.com>

On Thu, Jun 11, 2015 at 07:26:23PM -0400, Ruben Safir wrote:
> Lets say Apple decides that are going to take the Linux Kernel and
> alter it extensively, in order for it to work with a new hardware platform 
> that they created. And lets say don't return the code base to the public.  
> Now who is going to protect the license and sue them?  You have literaly 
> thousands of partiticpants who have standing now in this case.  Apple can just
> blow there nose at you if they are willing to put up with the bad publicity.

Like I tell companies all the time when they ask me about this, "Look at
the major copyright holders of the kernel, do you think your lawyers are
better than Intel and IBM's lawyers?"

And like Rik points out, you end up with thousands of different
companies and individuals who can enforce the license, which is a
wonderful thing to have and has worked out quite well so far.

So all is well, don't fret.

greg k-h

  parent reply	other threads:[~2015-06-12  0:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  9:19 Kernel contributions from organisations and individual privacy Chris Packham
2015-06-11  4:58 ` Jason Ball
2015-06-11  5:10   ` Chris Packham
2015-06-11  5:19     ` Ruben Safir
2015-06-11 14:28       ` Greg KH
2015-06-11 14:41         ` Ruben Safir
2015-06-11 15:38           ` Greg KH
2015-06-11 16:39             ` Ruben Safir
2015-06-11 17:54               ` Greg KH
2015-06-11 17:57               ` Greg KH
2015-06-11 23:26                 ` Ruben Safir
2015-06-11 23:37                   ` Rik van Riel
2015-06-11 23:55                     ` Ruben Safir
2015-06-12  0:13                     ` Jeff Haran
2015-06-12  1:28                       ` Rik van Riel
2015-06-12 23:29                         ` Jeff Haran
2015-06-13 15:40                           ` Bjørn Mork
2015-06-13 19:08                             ` Ruben Safir
2015-06-15 23:08                             ` Jeff Haran
2015-06-15 23:55                               ` Rik van Riel
2015-06-16 16:23                                 ` Jeff Haran
2015-06-13 16:23                           ` Rik van Riel
2015-06-14 21:18                           ` Valdis.Kletnieks at vt.edu
     [not found]                             ` <B424B28F-AB7E-4972-95BB-FF91D85D0FED@gmail.com>
2015-06-14 23:29                               ` Valdis.Kletnieks at vt.edu
     [not found]                                 ` <557E0FF7.1000607@gmail.com>
2015-06-15  2:08                                   ` Valdis.Kletnieks at vt.edu
2015-06-12  0:52                   ` Greg KH [this message]
2015-06-12  3:31                   ` Valdis.Kletnieks at vt.edu
2015-06-12  4:39                     ` Ruben Safir
2015-06-12  7:18                       ` Valdis.Kletnieks at vt.edu
2015-06-11 13:13     ` Rik van Riel
2015-06-11 14:27   ` Greg KH
2015-06-11 14:25 ` Greg KH

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=20150612005200.GB26737@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.