From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Sachin Saxena <sachin.saxena@nxp.com>,
ferruh.yigit@intel.com, hemant.agrawal@nxp.com,
techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] drivers: copyrights update for nxp files
Date: Wed, 06 Nov 2019 12:05:53 +0100 [thread overview]
Message-ID: <28095054.1JpxFQr51N@xps> (raw)
In-Reply-To: <20191106104346.3973-1-sachin.saxena@nxp.com>
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?
next prev parent reply other threads:[~2019-11-06 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 10:43 Sachin Saxena
2019-11-06 11:05 ` Thomas Monjalon [this message]
2019-11-18 14:16 ` Sachin Saxena
2019-11-28 9:57 ` Hemant Agrawal
2019-11-28 15:05 ` Thomas Monjalon
2019-11-06 12:59 [dpdk-dev] [PATCH] drivers: copyrights update for NXP files Sachin Saxena
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=28095054.1JpxFQr51N@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@nxp.com \
--cc=techboard@dpdk.org \
/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).