From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] driver: net: update copyright info
Date: Mon, 25 Mar 2019 09:58:11 -0400 [thread overview]
Message-ID: <20190325135811.GD18421@bill-the-cat> (raw)
In-Reply-To: <20190325153621.13726-1-pankaj.bansal@nxp.com>
On Mon, Mar 25, 2019 at 10:12:12AM +0000, Pankaj Bansal wrote:
> Update copyright info for the issues reported after running
> check-legal test.
>
> Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
> ---
>
> Notes:
> V2:
> - Removed past tense from commit description and body
>
> drivers/net/fsl-mc/mc.c | 3 +--
> drivers/net/ldpaa_eth/ldpaa_eth.c | 2 +-
> drivers/net/ldpaa_eth/ldpaa_eth.h | 2 +-
> drivers/net/ldpaa_eth/ldpaa_wriop.c | 1 +
> drivers/net/ldpaa_eth/lx2160a.c | 2 +-
> drivers/net/phy/phy.c | 2 ++
> include/fsl-mc/ldpaa_wriop.h | 1 +
> include/phy.h | 2 ++
> 8 files changed, 10 insertions(+), 5 deletions(-)
NAK. I see that NXP has not made code changes to the following files in
2019:
drivers/net/ldpaa_eth/ldpaa_eth.c
drivers/net/ldpaa_eth/ldpaa_eth.h
drivers/net/ldpaa_eth/ldpaa_wriop.c
include/fsl-mc/ldpaa_wriop.h
And drivers/net/phy/phy.c / include/phy.h really should be only 2018 as
Joe merged it in 2019, but NXP didn't do that:
commit b3eabd82f21b4d9206622fc5aee16751d2f4be8f
Author: Pankaj Bansal <pankaj.bansal@nxp.com>
AuthorDate: Fri Nov 16 06:26:18 2018 +0000
Commit: Joe Hershberger <joe.hershberger@ni.com>
CommitDate: Thu Jan 24 11:35:26 2019 -0600
net: phy: Add clause 45 identifier to phy_device
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190325/7cf35d94/attachment.sig>
prev parent reply other threads:[~2019-03-25 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 10:12 [U-Boot] [PATCH v2] driver: net: update copyright info Pankaj Bansal
2019-03-25 13:58 ` Tom Rini [this message]
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=20190325135811.GD18421@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.