From: "Rafał Miłecki" <rafal-g1n6cQUeyibVItvQsEIGlw@public.gmane.org>
To: xiaolei li <xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Cc: Daniel Thompson
<daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Ryder Lee <ryder.lee-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Masahiro Yamada
<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>,
Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>,
Miquel Raynal
<miquel.raynal-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>,
"Gustavo A. R. Silva"
<gustavo-L1vi/lXTdts+Va1GwOuvDg@public.gmane.org>,
jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
yingjoe.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
boris.brezillon-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org,
linux-mtd
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Wei Yongjun <weiyongjun1-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
yellowriver2010-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org,
Matthias Brugger
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
rogercc.lin-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Dan Carpenter
<dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
peterpandong-AL4WhLSQfzjQT0dZR+AlfA@public.gmane.org
Subject: Re: [RFC PATCH v4 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL
Date: Wed, 19 Jun 2019 12:49:00 +0200 [thread overview]
Message-ID: <ce02eca83c4d28f7ea32a586f25b0d35@milecki.pl> (raw)
In-Reply-To: <1560936760.19057.1.camel@mhfsdcap03>
On 2019-06-19 11:32, xiaolei li wrote:
> On Tue, 2019-06-18 at 11:36 +0200, Rafał Miłecki wrote:
>> On 2019-05-24 10:18, xiaolei li wrote:
>> > On Fri, 2019-05-24 at 09:55 +0200, Rafał Miłecki wrote:
>> >> On 2019-05-24 09:52, Arnd Bergmann wrote:
>> >> > On Tue, May 7, 2019 at 11:20 AM Xiaolei Li <xiaolei.li@mediatek.com>
>> >> > wrote:
>> >> >>
>> >> >> It is wanted 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 and replace license text with
>> >> >> SPDX tag.
>> >> >>
>> >> >> Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
>> >> >> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
>> >> >> Acked-by: Ryder Lee <ryder.lee@mediatek.com>
>> >> >> Acked-by: Rafał Miłecki <rafal@milecki.pl>
>> >> >> Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
>> >> >> Acked-by: Boris Brezillon <boris.brezillon@collabora.com>
>> >> >> Acked-by: RogerCC Lin <rogercc.lin@mediatek.com>
>> >> >
>> >> > Acked-by: Arnd Bergmann <arnd@arndb.de>
>> >> >
>> >> > Sorry for missing this earlier.
>> >>
>> >> Thank you!
>> >>
>> >> Xiaolei: please resend this patch without RFC in a subject. I believe
>> >> it
>> >> can be applied/pushed now.
>> >
>> > Thanks very much for your response!
>> > I will send a formal patch soon.
>>
>> Hi Xiaolei, what's the status of this?
>>
>> It took some effort to sort that licensing out, I believe handling
>> this
>> sooner than later is highly recommended.
>
> Thanks for your attention.
> I sent the formal patch about two weeks ago. So, you didn't receive it,
> right ?
It has never reached me or mailing list.
See:
http://lists.infradead.org/pipermail/linux-mtd/2019-June/thread.html
https://patchwork.ozlabs.org/project/linux-mtd/list/?series=&submitter=71599&state=*&q=&archive=&delegate=
The latest one is RFC v4.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2019-06-19 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 9:20 [RFC PATCH v4 0/1] Re-license MTK NAND driver Xiaolei Li
2019-05-07 9:20 ` [RFC PATCH v4 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL Xiaolei Li
[not found] ` <20190507092020.1917-2-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-05-07 10:06 ` Miquel Raynal
2019-05-07 10:18 ` xiaolei li
2019-05-07 10:48 ` Rafał Miłecki
[not found] ` <3edbd5a4-4226-4cec-052a-81f7251817a1-g1n6cQUeyibVItvQsEIGlw@public.gmane.org>
2019-05-17 1:42 ` xiaolei li
2019-05-24 7:52 ` Arnd Bergmann
2019-05-24 7:55 ` Rafał Miłecki
[not found] ` <5052ea548ce89c1a588236d00319960b-g1n6cQUeyibVItvQsEIGlw@public.gmane.org>
2019-05-24 8:18 ` xiaolei li
2019-06-18 9:36 ` Rafał Miłecki
[not found] ` <75974a2066425e5852d0295b22d2b259-g1n6cQUeyibVItvQsEIGlw@public.gmane.org>
2019-06-19 9:32 ` xiaolei li
2019-06-19 10:49 ` Rafał Miłecki [this message]
2019-06-20 1:14 ` xiaolei li
[not found] ` <CAK8P3a3d-2U=hpb0P0+W-eZ0cviwKVwy6dWvHbhBCgF4CJUWKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-24 7:56 ` Masahiro Yamada
2019-05-07 9:40 ` [RFC PATCH v4 0/1] Re-license MTK NAND driver Dan Carpenter
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=ce02eca83c4d28f7ea32a586f25b0d35@milecki.pl \
--to=rafal-g1n6cqueyibvitvqseiglw@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=boris.brezillon-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=gustavo-L1vi/lXTdts+Va1GwOuvDg@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=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=miquel.raynal-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org \
--cc=peterpandong-AL4WhLSQfzjQT0dZR+AlfA@public.gmane.org \
--cc=richard-/L3Ra7n9ekc@public.gmane.org \
--cc=rogercc.lin-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=ryder.lee-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=weiyongjun1-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org \
--cc=yellowriver2010-PkbjNfxxIARBDgjK7y7TUQ@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