linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xiaolei li <xiaolei.li@mediatek.com>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: daniel.thompson@linaro.org, ryder.lee@mediatek.com,
	srv_heupstream@mediatek.com, richard@nod.at,
	miquel.raynal@bootlin.com, jorge.ramirez-ortiz@linaro.org,
	yingjoe.chen@mediatek.com, boris.brezillon@collabora.com,
	linux-mtd@lists.infradead.org, yellowriver2010@hotmail.com,
	matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org
Subject: Re: [RFC PATCH v3 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL
Date: Mon, 6 May 2019 08:56:20 +0800	[thread overview]
Message-ID: <1557104180.26455.89.camel@mhfsdcap03> (raw)
In-Reply-To: <79539034414767c95e456a79391a18e7@milecki.pl>

Hi Rafal,

On Sun, 2019-05-05 at 17:06 +0200, Rafał Miłecki wrote:
> On 2019-05-05 11:12, xiaolei li wrote:
> > Up to now,
> > Xiaolei Li <xiaolei.li@mediatek.com> (the author and major 
> > contributor),
> > Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> (the author and
> > major contributor),
> > Ryder Lee <ryder.lee@mediatek.com> (developer),
> > Rafał Miłecki <rafal@milecki.pl> (developer)
> > sent ACK for this RFC patch.
> > 
> > May I ask if it is enough to accept this change? Or should I wait for
> > other developer's response?
> 
> I can't imagine re-licensing someone's work without a permission.

I have no intention to offend other's contribution.
That is why I sent this RFC patch to ask for ACKs from contributors.

> 
> The best you can do is ignoring contributors that submitted changes that
> aren't really copyrightable (something like fixing a comment typo, some
> auto-generated diff-s).
> 
> I used following command to check mtk_nand.c file history:
> # git log --follow drivers/mtd/nand/raw/mtk_nand.c | grep 
> "Signed-off-by" | sort | uniq -c | sort -r -n
>       19     Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>       18     Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
>       15     Signed-off-by: Boris Brezillon 
> <boris.brezillon@free-electrons.com>
>        6     Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
>        3     Signed-off-by: RogerCC Lin <rogercc.lin@mediatek.com>
>        2     Signed-off-by: Miquel Raynal 
> <miquel.raynal@free-electrons.com>
>        1     Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
>        1     Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
>        1     Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>        1     Signed-off-by: Peter Pan <peterpandong@micron.com>
>        1     Signed-off-by: Masahiro Yamada 
> <yamada.masahiro@socionext.com>
>        1     Signed-off-by: Jorge Ramirez-Ortiz 
> <jorge.ramirez-ortiz@linaro.org>
> 
> Ideally you should still get acks from:
> 
> 1) Miquel
> Contributor of 21 changes
> 
> 2) Boris
> Contributor of 33 changes
> 
> 3) RogerCC
> Contributor of 3 changes:
> 98dea8d71931 ("mtd: nand: mtk: Support MT7622 NAND flash controller.")
> b45ee5501ede ("mtd: nand: mtk: Support different MTK NAND flash 
> controller IP")
> 559e58e7ed2d ("mtd: nand: fix chances to create incomplete ECC data when 
> writing")
> 
> 4) Wei
> Contributor of 1 change:
> 07f76443ef81 ("mtd: nand: mediatek: remove redundant dev_err call in 
> mtk_nfc_probe()")
> 
> 5) Peter
> Contributor of 1 change:
> d4092d76a4a4 ("mtd: nand: Rename nand.h into rawnand.h")
> 
> 6) Masahiro
> Contributor of 1 change:
> f0dbe4aa35e7 ("mtd: nand: mediatek: return error code of 
> nand_scan_ident/tail() on error")
> 
> I guess we could accept your patch without acks from Wei, Peter and 
> Masahiro.
> 
> You definitely need an approval from Miquel, Boris and RogerCC.
> 
> It doesn't seem you took this re-licensing task too seriously.
> 
> Please pay more attention to this licensing problem, you can start with 
> doing
> a similar research for mtk_ecc.c and mtk_ecc.h.

Thanks for your ACK and good suggestion. It is really helpful for me.

Thanks,
Xiaolei


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-05-06  0:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29  8:51 [RFC PATCH v3 0/1] Re-license MTK NAND driver Xiaolei Li
2019-04-29  8:51 ` [RFC PATCH v3 1/1] mtd: rawnand: mtk: Re-license MTK NAND driver as Dual MIT/GPL Xiaolei Li
2019-04-29  9:41   ` Rafał Miłecki
2019-04-29 10:02     ` xiaolei li
2019-05-05  9:12     ` xiaolei li
2019-05-05 15:06       ` Rafał Miłecki
2019-05-06  0:56         ` xiaolei li [this message]
2019-05-06  8:09           ` Miquel Raynal
2019-05-06  8:18           ` Boris Brezillon
2019-05-06  9:11             ` xiaolei li
2019-05-07  8:40               ` RogerCC.Lin
2019-05-07  8:42               ` RogerCC.Lin

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=1557104180.26455.89.camel@mhfsdcap03 \
    --to=xiaolei.li@mediatek.com \
    --cc=boris.brezillon@collabora.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=matthias.bgg@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    --cc=ryder.lee@mediatek.com \
    --cc=srv_heupstream@mediatek.com \
    --cc=yellowriver2010@hotmail.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;
as well as URLs for NNTP newsgroup(s).