linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 3/7] brcmsmac: switch source files to using SPDX license identifier
Date: Mon, 8 Jul 2019 12:41:18 +0200	[thread overview]
Message-ID: <20190708104118.GA10261@kroah.com> (raw)
In-Reply-To: <34aa04e4-9ddd-b6aa-721f-a20398f7740d@broadcom.com>

On Mon, Jul 08, 2019 at 12:07:43PM +0200, Arend Van Spriel wrote:
> + Alan
> 
> On 5/17/2019 8:07 PM, Rafał Miłecki wrote:
> > > > > Another option could be MIT license which is in the preferred folder.
> > > > > Will have to consult our legal department about it though.
> > > > Hey, if your legal department is going to get asked this, why not just
> > > > switch it to GPLv2?  That would make everything much simpler.
> > > Hah. Because I already know the answer to that.;-)
> > It's not that obvious to me, sorry. Does your legal department require
> > something more permissive than GPLv2? Is that worth asking them about
> > dual-licensing? Something like
> > GPL-2.0 OR MIT
> > ? That assures driver is compatible with Linux, no matter what's the
> > current lawyers interpretation of MIT vs. GPL 2.0. I believe Alan Cox
> > once told/suggested that dual-licensing is safer for legal reasons.
> 
> Hi Alan,
> 
> Rafał mentioned your name a while ago when I was struggling with the SPDX
> identifiers. The drivers sources I want to modify for this originally had a
> license text in the header that matches ISC. However,
> one of the files did not have that and it was marked in bulk to GPLv2. So
> now the question is whether I can change it to ISC like the rest or should I
> make it dual like Rafał suggested.
> 
> Can you elaborate the pros and cons of dual license?

You need to talk to your lawyers about that.  Please ask this of them.

thanks,

greg k-h

  reply	other threads:[~2019-07-08 10:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 12:04 [PATCH 0/7] brcm80211: SPDX tags and Kconfig cleanup Arend van Spriel
2019-05-16 12:04 ` [PATCH 1/7] brcm80211: switch common header files to using SPDX license identifier Arend van Spriel
2019-05-16 20:57   ` Arend Van Spriel
2019-05-17 18:04     ` Arend Van Spriel
2019-05-20 16:54       ` Kalle Valo
2019-05-21  8:11         ` Arend Van Spriel
2019-05-23  9:17           ` Kalle Valo
2019-05-23 10:53             ` Arend Van Spriel
2019-05-28 12:24   ` Kalle Valo
2019-05-16 12:04 ` [PATCH 2/7] brcmutil: switch source " Arend van Spriel
2019-05-16 12:04 ` [PATCH 3/7] brcmsmac: " Arend van Spriel
2019-05-16 17:31   ` Greg Kroah-Hartman
2019-05-16 19:45     ` Arend Van Spriel
2019-05-16 20:01       ` Greg Kroah-Hartman
2019-05-16 20:15         ` Arend Van Spriel
2019-05-17 18:07           ` Rafał Miłecki
2019-05-17 18:22             ` Arend Van Spriel
2019-07-08 10:07             ` Arend Van Spriel
2019-07-08 10:41               ` Greg Kroah-Hartman [this message]
2019-05-23  9:16   ` Kalle Valo
2019-05-16 12:04 ` [PATCH 4/7] brcmsmac: switch phy " Arend van Spriel
2019-05-16 12:04 ` [PATCH 5/7] brcmfmac: switch " Arend van Spriel
2019-05-16 12:04 ` [PATCH 6/7] brcmfmac: use separate Kconfig file for brcmfmac Arend van Spriel
2019-05-16 12:04 ` [PATCH 7/7] brcm80211: select WANT_DEV_COREDUMP conditionally " Arend van Spriel

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=20190708104118.GA10261@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arend.vanspriel@broadcom.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zajec5@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).