From: Sachin Saxena <sachin.saxena@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] drivers: copyrights update for NXP files
Date: Wed, 6 Nov 2019 12:59:12 +0000 [thread overview]
Message-ID: <VI1PR04MB48454D2B36141D673C3668CCE3790@VI1PR04MB4845.eurprd04.prod.outlook.com> (raw)
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, November 6, 2019 4:36 PM
> To: dev@dpdk.org
> Cc: Sachin Saxena <sachin.saxena@nxp.com>; ferruh.yigit@intel.com;
> Hemant Agrawal <hemant.agrawal@nxp.com>; techboard@dpdk.org
> Subject: Re: [PATCH] drivers: copyrights update for nxp files
> Importance: High
>
> 06/11/2019 11:43, Sachin Saxena:
> > --- a/drivers/bus/dpaa/base/fman/fman.c
> > +++ b/drivers/bus/dpaa/base/fman/fman.c
> > @@ -1,7 +1,7 @@
> > /* SPDX-License-Identifier: (BSD-3-Clause OR GPL-2.0)
> > *
> > * Copyright 2010-2016 Freescale Semiconductor Inc.
> > - * Copyright 2017 NXP
> > + * Copyright 2017-2019 NXP
>
> I am not sure we need such change, especially when the file is not modified.
>
> Could we have a clear answer from someone who knows someone who
> knows a lawyer?
> What is the value of these date ranges in the copyright?
>
[Sachin Saxena] Hello Thomas. Actually the files includes in this patch have been updated in current year through
different patches and NXP legal department mandate us to update the NXP Copyright year(or Range) in all touched files.
We missed to update the same in relevant patches so initiated this specific copyright update patch request.
Hope this answers your query.
next reply other threads:[~2019-11-06 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:59 Sachin Saxena [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 10:43 [dpdk-dev] [PATCH] drivers: copyrights update for nxp files Sachin Saxena
2019-11-06 11:05 ` Thomas Monjalon
2019-11-18 14:16 ` Sachin Saxena
2019-11-28 9:57 ` Hemant Agrawal
2019-11-28 15:05 ` Thomas Monjalon
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=VI1PR04MB48454D2B36141D673C3668CCE3790@VI1PR04MB4845.eurprd04.prod.outlook.com \
--to=sachin.saxena@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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).