From: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
To: Xiaolei Li <xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Cc: daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
miquel.raynal-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org,
jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
yingjoe.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL
Date: Wed, 24 Apr 2019 09:29:48 +0200 [thread overview]
Message-ID: <1868653.V2KA8McHNA@blindfold> (raw)
In-Reply-To: <20190424064522.33501-2-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
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.
Thanks,
//richard
next prev parent reply other threads:[~2019-04-24 7:29 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
[not found] ` <20190424064522.33501-1-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-04-24 6:45 ` [RFC PATCH 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL Xiaolei Li
[not found] ` <20190424064522.33501-2-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-04-24 7:29 ` Richard Weinberger [this message]
2019-04-24 8:25 ` xiaolei li
2019-04-24 13:15 ` Matthias Brugger
[not found] ` <5c674c6c-7df7-d452-8971-53caeff82a3f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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=1868653.V2KA8McHNA@blindfold \
--to=richard-/l3ra7n9ekc@public.gmane.org \
--cc=boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org \
--cc=daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=miquel.raynal-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=yingjoe.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox