[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANh8QzwPmbfr1y9Yz7ctbannX3gOWZBQG1_xDM6xit=3ZXD+pg@mail.gmail.com>
Date: Wed, 18 Mar 2020 09:27:53 +0100
From: "Fuzzey, Martin" <martin.fuzzey@...wbird.group>
To: Andy Duan <fugang.duan@....com>
Cc: Rob Herring <robh+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Fabio Estevam <festevam@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
dl-linux-imx <linux-imx@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [EXT] [PATCH 0/4] Fix Wake on lan with FEC on i.MX6
Hi Andy,
On Wed, 18 Mar 2020 at 07:28, Andy Duan <fugang.duan@....com> 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.
>
Ok, looks like it was originally from you, should I add your current
email address or the one at the time (B38611@...escale.com)?
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
Powered by blists - more mailing lists