From: Christoph Lameter <cl@linux.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] GPL enforcement actions
Date: Fri, 31 Jul 2015 13:45:08 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1507311342380.14357@east.gentwo.org> (raw)
In-Reply-To: <559C3F56.8040606@roeck-us.net>
On Tue, 7 Jul 2015, Guenter Roeck wrote:
> ... and then have the LF attorneys brief LF member companies about the
> outcome of the meeting. I always find those legal briefings very useful.
One subject that I would like to have some clarification on is relicensing
of in-kernel-code. There were a couple of license changes recently from
GPL to "pick onee GPL or BSD" in the infiniband stack. I was a bit
surprised by that being possible.
Presumably the copyright holders have to agree to this. What exactly
qualifies to be a copyright holder? If one is mentioned in the file
header? If one modified a line of code in the file?
next prev parent reply other threads:[~2015-07-31 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 8:06 David Woodhouse
2015-07-04 10:18 ` David Howells
2015-07-04 16:49 ` David Woodhouse
2015-07-07 18:34 ` Steven Rostedt
2015-07-07 19:51 ` David Woodhouse
2015-07-07 20:00 ` Greg KH
2015-07-07 20:18 ` David Woodhouse
2015-07-07 22:11 ` John W. Linville
2015-07-08 15:41 ` Tim Bird
2015-07-08 21:25 ` Greg KH
2015-07-08 22:55 ` Tim Bird
2015-07-07 20:33 ` Chris Mason
2015-07-07 22:15 ` Luck, Tony
2015-07-07 23:55 ` Chris Mason
2015-07-07 21:06 ` Guenter Roeck
2015-07-31 18:45 ` Christoph Lameter [this message]
2015-07-31 19:06 ` James Bottomley
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=alpine.DEB.2.11.1507311342380.14357@east.gentwo.org \
--to=cl@linux.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux@roeck-us.net \
/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