From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, shaibran@amazon.com
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [PATCH 07/15] net/ena/base: update copyrights comments
Date: Mon, 8 Jul 2024 09:38:37 +0530 [thread overview]
Message-ID: <3cfddde7-6b3d-8350-c664-12c0a6bfa0dd@oss.nxp.com> (raw)
In-Reply-To: <26909df4-4858-41a3-a523-f8b567dc26e6@amd.com>
On 08-07-2024 00:27, Ferruh Yigit wrote:
> On 7/2/2024 3:46 PM, shaibran@amazon.com wrote:
>> From: Shai Brandes <shaibran@amazon.com>
>>
>> copyright dates are not mandatory to be maintained,
>> therefore the range of years was removed.
>> In addition, the copyrights lines were separated
>> into two comments.
>>
>> Signed-off-by: Shai Brandes <shaibran@amazon.com>
>> ---
>> drivers/net/ena/base/ena_com.c | 4 ++--
>> drivers/net/ena/base/ena_com.h | 4 ++--
>> drivers/net/ena/base/ena_defs/ena_admin_defs.h | 5 +++--
>> drivers/net/ena/base/ena_defs/ena_common_defs.h | 4 ++--
>> drivers/net/ena/base/ena_defs/ena_eth_io_defs.h | 5 +++--
>> drivers/net/ena/base/ena_defs/ena_includes.h | 4 ++--
>> drivers/net/ena/base/ena_defs/ena_regs_defs.h | 4 ++--
>> drivers/net/ena/base/ena_eth_com.c | 4 ++--
>> drivers/net/ena/base/ena_eth_com.h | 4 ++--
>> drivers/net/ena/base/ena_plat.h | 4 ++--
>> drivers/net/ena/base/ena_plat_dpdk.h | 4 ++--
>> 11 files changed, 24 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/net/ena/base/ena_com.c b/drivers/net/ena/base/ena_com.c
>> index ad4f3f9431..5f46e692b3 100644
>> --- a/drivers/net/ena/base/ena_com.c
>> +++ b/drivers/net/ena/base/ena_com.c
>> @@ -1,5 +1,5 @@
>> -/* SPDX-License-Identifier: BSD-3-Clause
>> - * Copyright (c) 2015-2020 Amazon.com, Inc. or its affiliates.
>> +/* SPDX-License-Identifier: BSD-3-Clause */
>> +/* Copyright (c) Amazon.com, Inc. or its affiliates.
>> * All rights reserved.
>> */
>>
> Hi Shai,
>
> I don't know about implication of dropping the copyright year
> altogether, we need to ask to an expert.
>
> What I know is, a copyright expires after some year, so to hold the
> copyright, there needs to be a starting point. And people use ranges to
> extend this copyright year.
>
>
> Instead of removing the year altogether, it make sense to me to just
> keep the initial year and don't add range later as code updated, this
> also will be more consistent with rest of the code.
> Let me drop this patch from the set, and learn more from the experts. It
> can be included later, I don't think this is something urgent.
>
>
> Another aspect is, the history of a source file can be acquired from the
> pubic git repository, so when it is first merged, when updated, all
> these information is available.
> So this feels like no need to record these days in the source code files
> but I don't know if these git repository metadata information is legally
> valid and accepted.
>
>
> And I am not quite sure if it has really any value to worry about
> copyright for a publicly available device driver code anyway, but this
> is not my domain.
Hi Shai,
Will you please just update the copyright year instead of removing
the year completely? e.g. 2015-2020, 2024 or 2015-2024
-Hemant
next prev parent reply other threads:[~2024-07-08 4:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:46 [PATCH 00/15] net/ena: driver release 2.10.0 shaibran
2024-07-02 14:46 ` [PATCH 01/15] net/ena/base: add descriptor dump capability shaibran
2024-07-02 14:46 ` [PATCH 02/15] net/ena/base: remove unused param shaibran
2024-07-02 14:46 ` [PATCH 03/15] net/ena/base: remove redundant assert checks shaibran
2024-07-02 14:46 ` [PATCH 04/15] net/ena/base: update memory barrier comment shaibran
2024-07-02 14:46 ` [PATCH 05/15] net/ena/base: add method to check used entries shaibran
2024-07-02 14:46 ` [PATCH 06/15] net/ena/base: add an additional reset reason shaibran
2024-07-02 14:46 ` [PATCH 07/15] net/ena/base: update copyrights comments shaibran
2024-07-07 18:57 ` Ferruh Yigit
2024-07-08 4:08 ` Hemant Agrawal [this message]
2024-07-08 7:02 ` Brandes, Shai
2024-07-08 8:38 ` Ferruh Yigit
2024-07-08 8:48 ` Brandes, Shai
2024-07-08 11:45 ` Ferruh Yigit
2024-07-02 14:46 ` [PATCH 08/15] net/ena/base: add macro for bitfield access shaibran
2024-07-02 14:46 ` [PATCH 09/15] net/ena: logger change to improve performance shaibran
2024-07-02 14:46 ` [PATCH 10/15] net/ena: rework device uninit shaibran
2024-07-02 14:46 ` [PATCH 11/15] net/ena: fix bad checksum handling shaibran
2024-07-02 14:46 ` [PATCH 12/15] net/ena: fix invalid return value check shaibran
2024-07-07 18:57 ` Ferruh Yigit
2024-07-02 14:46 ` [PATCH 13/15] net/ena: fix wrong handling of checksum shaibran
2024-07-02 14:46 ` [PATCH 14/15] net/ena: rework Rx checksum inspection shaibran
2024-07-02 14:46 ` [PATCH 15/15] net/ena: upgrade driver version to 2.10.0 shaibran
2024-07-07 19:11 ` [PATCH 00/15] net/ena: driver release 2.10.0 Ferruh Yigit
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=3cfddde7-6b3d-8350-c664-12c0a6bfa0dd@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=hemant.agrawal@nxp.com \
--cc=shaibran@amazon.com \
/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).