From: xiaolei li <xiaolei.li@mediatek.com>
To: Richard Weinberger <richard@nod.at>
Cc: daniel.thompson@linaro.org, srv_heupstream@mediatek.com,
miquel.raynal@bootlin.com, jorge.ramirez-ortiz@linaro.org,
boris.brezillon@bootlin.com, linux-mediatek@lists.infradead.org,
yingjoe.chen@mediatek.com, linux-mtd@lists.infradead.org
Subject: Re: [RFC PATCH 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL
Date: Wed, 24 Apr 2019 16:25:47 +0800 [thread overview]
Message-ID: <1556094347.26455.5.camel@mhfsdcap03> (raw)
In-Reply-To: <1868653.V2KA8McHNA@blindfold>
Hi Richard,
On Wed, 2019-04-24 at 09:29 +0200, Richard Weinberger wrote:
> Am Mittwoch, 24. April 2019, 08:45:22 CEST schrieb Xiaolei Li:
> > It is allowed to use MTK NAND 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.
>
> I fear this needs ACKs from all authors and major contributors of the driver
> before we can apply such a change.
Yes. MTK wants to solicit ACKs for this change from copyrights holders
here.
I added another driver author Jorge, and let's wait for the response.
Thanks,
Xiaolei
>
> Thanks,
> //richard
>
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-04-24 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 6:45 [RFC PATCH 0/1] Re-license MTK NAND driver Xiaolei Li
2019-04-24 6:45 ` [RFC PATCH 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL Xiaolei Li
2019-04-24 7:29 ` Richard Weinberger
2019-04-24 8:25 ` xiaolei li [this message]
2019-04-24 13:15 ` Matthias Brugger
2019-04-25 1:12 ` xiaolei li
2019-04-24 16:15 ` Jorge Ramirez
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=1556094347.26455.5.camel@mhfsdcap03 \
--to=xiaolei.li@mediatek.com \
--cc=boris.brezillon@bootlin.com \
--cc=daniel.thompson@linaro.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.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