All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leilk Liu <leilk.liu@mediatek.com>
Cc: Mark Brown <broonie@kernel.org>,
	Nicolas Boichat <drinkcat@chromium.org>,
	"luhua . xu" <luhua.xu@mediatek.com>,
	Wei Yongjun <weiyj.lk@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <swboyd@chromium.org>,
	Pi-Hsun Shih <pihsun@chromium.org>,
	Markus Elfring <elfring@users.sourceforge.net>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Daniel Kurtz <djkurtz@chromium.org>,
	Axel Lin <axel.lin@ingics.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
	linux-mediatek@lists.infradead.org, fparent@baylibre.com
Subject: Re: [PATCH] spi: mediatek: Re-license MTK SPI driver as Dual MIT/GPL
Date: Wed, 3 Mar 2021 10:12:46 +0100	[thread overview]
Message-ID: <YD9TDv85D/zSV2Li@kroah.com> (raw)
In-Reply-To: <1614762159.5898.9.camel@mhfsdcap03>

On Wed, Mar 03, 2021 at 05:02:39PM +0800, Leilk Liu wrote:
> On Wed, 2021-03-03 at 08:18 +0100, Greg Kroah-Hartman wrote:
> > On Wed, Mar 03, 2021 at 10:56:36AM +0800, Leilk Liu wrote:
> > > From: "leilk.liu" <leilk.liu@mediatek.com>
> > > 
> > > It is wanted to use MTK spi bus driver with GPL-2.0 or MIT license.
> > > But now it is only licensed as GPL-2.0, so re-license it as dual
> > > MIT/GPL.
> > > 
> > > Signed-off-by: leilk.liu <leilk.liu@mediatek.com>
> > 
> > Please use your name here, not an email alias for where your name goes.
> > 
> OK, I'll fix it, thanks!
> > 
> > > ---
> > >  drivers/spi/spi-mt65xx.c                 | 4 ++--
> > >  include/linux/platform_data/spi-mt65xx.h | 2 +-
> > 
> > Given that these files have been licensed under the GPL only since 2015,
> > all changes contributed to it have only been licensed under the GPL as
> > well, so have you gotten approval for all of the contributors for this
> > change?
> > 
> This is the reason that I sent this patch to ask for ACKs from all
> contributors (who are all in the To mail-list) for these files.

That wasn't obvious :)

But given that many of the contributors here do not actually own the
copyrights of their contributions, how can you be sure that the real
owners are agreeing to this?  That requires something much more "legal"
than just an "ack" on a patch.  Please work with your corporate lawyers
for how to do this correctly.

> > Can you please get your lawyer to also sign off on this license change
> > patch, so that we know that you have their approval for this incase
> > there are questions about it in the future?
> > 
> I need to use the code in other projects that is not with GPL-2.0.

What project needs this code that you can not just base it off of your
original contribution instead?  That would not require any license
change of the kernel files, right?  Wouldn't that be easier than trying
to retain this license change over time as you will not be taking the
changes here into another project as well.

> Also, the license change is approved by Mediatek supervisor.

Great, get them to also sign-off on the patch please, along with your
lawyers, so that we know all is done correctly.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leilk Liu <leilk.liu@mediatek.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-mediatek@lists.infradead.org,
	Nicolas Boichat <drinkcat@chromium.org>,
	Wei Yongjun <weiyj.lk@gmail.com>,
	fparent@baylibre.com, linux-spi@vger.kernel.org,
	linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Mark Brown <broonie@kernel.org>,
	"luhua . xu" <luhua.xu@mediatek.com>,
	Pi-Hsun Shih <pihsun@chromium.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Axel Lin <axel.lin@ingics.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Markus Elfring <elfring@users.sourceforge.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: mediatek: Re-license MTK SPI driver as Dual MIT/GPL
Date: Wed, 3 Mar 2021 10:12:46 +0100	[thread overview]
Message-ID: <YD9TDv85D/zSV2Li@kroah.com> (raw)
In-Reply-To: <1614762159.5898.9.camel@mhfsdcap03>

On Wed, Mar 03, 2021 at 05:02:39PM +0800, Leilk Liu wrote:
> On Wed, 2021-03-03 at 08:18 +0100, Greg Kroah-Hartman wrote:
> > On Wed, Mar 03, 2021 at 10:56:36AM +0800, Leilk Liu wrote:
> > > From: "leilk.liu" <leilk.liu@mediatek.com>
> > > 
> > > It is wanted to use MTK spi bus driver with GPL-2.0 or MIT license.
> > > But now it is only licensed as GPL-2.0, so re-license it as dual
> > > MIT/GPL.
> > > 
> > > Signed-off-by: leilk.liu <leilk.liu@mediatek.com>
> > 
> > Please use your name here, not an email alias for where your name goes.
> > 
> OK, I'll fix it, thanks!
> > 
> > > ---
> > >  drivers/spi/spi-mt65xx.c                 | 4 ++--
> > >  include/linux/platform_data/spi-mt65xx.h | 2 +-
> > 
> > Given that these files have been licensed under the GPL only since 2015,
> > all changes contributed to it have only been licensed under the GPL as
> > well, so have you gotten approval for all of the contributors for this
> > change?
> > 
> This is the reason that I sent this patch to ask for ACKs from all
> contributors (who are all in the To mail-list) for these files.

That wasn't obvious :)

But given that many of the contributors here do not actually own the
copyrights of their contributions, how can you be sure that the real
owners are agreeing to this?  That requires something much more "legal"
than just an "ack" on a patch.  Please work with your corporate lawyers
for how to do this correctly.

> > Can you please get your lawyer to also sign off on this license change
> > patch, so that we know that you have their approval for this incase
> > there are questions about it in the future?
> > 
> I need to use the code in other projects that is not with GPL-2.0.

What project needs this code that you can not just base it off of your
original contribution instead?  That would not require any license
change of the kernel files, right?  Wouldn't that be easier than trying
to retain this license change over time as you will not be taking the
changes here into another project as well.

> Also, the license change is approved by Mediatek supervisor.

Great, get them to also sign-off on the patch please, along with your
lawyers, so that we know all is done correctly.

thanks,

greg k-h

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leilk Liu <leilk.liu@mediatek.com>
Cc: Mark Brown <broonie@kernel.org>,
	Nicolas Boichat <drinkcat@chromium.org>,
	"luhua . xu" <luhua.xu@mediatek.com>,
	Wei Yongjun <weiyj.lk@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <swboyd@chromium.org>,
	Pi-Hsun Shih <pihsun@chromium.org>,
	Markus Elfring <elfring@users.sourceforge.net>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Daniel Kurtz <djkurtz@chromium.org>,
	Axel Lin <axel.lin@ingics.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
	linux-mediatek@lists.infradead.org, fparent@baylibre.com
Subject: Re: [PATCH] spi: mediatek: Re-license MTK SPI driver as Dual MIT/GPL
Date: Wed, 3 Mar 2021 10:12:46 +0100	[thread overview]
Message-ID: <YD9TDv85D/zSV2Li@kroah.com> (raw)
In-Reply-To: <1614762159.5898.9.camel@mhfsdcap03>

On Wed, Mar 03, 2021 at 05:02:39PM +0800, Leilk Liu wrote:
> On Wed, 2021-03-03 at 08:18 +0100, Greg Kroah-Hartman wrote:
> > On Wed, Mar 03, 2021 at 10:56:36AM +0800, Leilk Liu wrote:
> > > From: "leilk.liu" <leilk.liu@mediatek.com>
> > > 
> > > It is wanted to use MTK spi bus driver with GPL-2.0 or MIT license.
> > > But now it is only licensed as GPL-2.0, so re-license it as dual
> > > MIT/GPL.
> > > 
> > > Signed-off-by: leilk.liu <leilk.liu@mediatek.com>
> > 
> > Please use your name here, not an email alias for where your name goes.
> > 
> OK, I'll fix it, thanks!
> > 
> > > ---
> > >  drivers/spi/spi-mt65xx.c                 | 4 ++--
> > >  include/linux/platform_data/spi-mt65xx.h | 2 +-
> > 
> > Given that these files have been licensed under the GPL only since 2015,
> > all changes contributed to it have only been licensed under the GPL as
> > well, so have you gotten approval for all of the contributors for this
> > change?
> > 
> This is the reason that I sent this patch to ask for ACKs from all
> contributors (who are all in the To mail-list) for these files.

That wasn't obvious :)

But given that many of the contributors here do not actually own the
copyrights of their contributions, how can you be sure that the real
owners are agreeing to this?  That requires something much more "legal"
than just an "ack" on a patch.  Please work with your corporate lawyers
for how to do this correctly.

> > Can you please get your lawyer to also sign off on this license change
> > patch, so that we know that you have their approval for this incase
> > there are questions about it in the future?
> > 
> I need to use the code in other projects that is not with GPL-2.0.

What project needs this code that you can not just base it off of your
original contribution instead?  That would not require any license
change of the kernel files, right?  Wouldn't that be easier than trying
to retain this license change over time as you will not be taking the
changes here into another project as well.

> Also, the license change is approved by Mediatek supervisor.

Great, get them to also sign-off on the patch please, along with your
lawyers, so that we know all is done correctly.

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-03 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  2:56 [PATCH] spi: mediatek: Re-license MTK SPI driver as Dual MIT/GPL Leilk Liu
2021-03-03  2:56 ` Leilk Liu
2021-03-03  3:05 ` Axel Lin
2021-03-03  3:05   ` Axel Lin
2021-03-03  3:05   ` Axel Lin
2021-03-03  7:18 ` Greg Kroah-Hartman
2021-03-03  7:18   ` Greg Kroah-Hartman
2021-03-03  7:18   ` Greg Kroah-Hartman
2021-03-03  9:02   ` Leilk Liu
2021-03-03  9:02     ` Leilk Liu
2021-03-03  9:02     ` Leilk Liu
2021-03-03  9:12     ` Greg Kroah-Hartman [this message]
2021-03-03  9:12       ` Greg Kroah-Hartman
2021-03-03  9:12       ` Greg Kroah-Hartman

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=YD9TDv85D/zSV2Li@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axel.lin@ingics.com \
    --cc=broonie@kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=drinkcat@chromium.org \
    --cc=elfring@users.sourceforge.net \
    --cc=fengguang.wu@intel.com \
    --cc=fparent@baylibre.com \
    --cc=javier@osg.samsung.com \
    --cc=leilk.liu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=luhua.xu@mediatek.com \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pihsun@chromium.org \
    --cc=swboyd@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=weiyj.lk@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 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.