From: Fuzzey, Martin <martin.fuzzey@flowbird.group> Sent: Wednesday, March 18, 2020 4:28 PM > Hi Andy, > > > On Wed, 18 Mar 2020 at 07:28, Andy Duan <fugang.duan@xxxxxxx> wrote: > > > > > > The most of code is reused from nxp internal tree, If you refer the > > patches from nxp kernel tree, please keep the signed-off with original > > author. > > It doesn't matter, I am happy you upstream the patch. Just keep: Signed-off-by: Fugang Duan <fugang.duan@xxxxxxx> > > Ok, looks like it was originally from you, should I add your current email > address or the one at the time (B38611@xxxxxxxxxxxxx)? > > Actually I don't have the NXP tree but a Digi tree, which is probably based on > it. > > I think, generally, this is a bit of a grey area. > > While I would always keep a SoB if I base a patch on an old mailing list patch > submission (and contact the person if possible first to > ask) I'm not sure if a SoB from a "random git tree" indicates they wish a > mainline submission with their name (some people may want credit and > others not want to be considered responsible for bugs...). > I didn't see a submission of this version (with the gpr information coming from > the DT) on the mailing lists, only the initial version using the platform callback > that was NAKd (I may have missed it though). > > Regards, > > Martin
