DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Maciej Bielski <mba@semihalf.com>, dev@dpdk.org
Cc: Marcin Wojtas <mw@semihalf.com>,
	Michal Krawczyk <mk@semihalf.com>,
	Guy Tzalik <gtzalik@amazon.com>,
	Evgeny Schemeilin <evgenys@amazon.com>
Subject: Re: [dpdk-dev] [PATCH] net/ena: change license clause to SPDX tags
Date: Thu, 26 Sep 2019 18:47:00 +0100	[thread overview]
Message-ID: <897ca5c8-92d3-5639-7de2-484f06848868@intel.com> (raw)
In-Reply-To: <20190926123109.2905-1-mba@semihalf.com>

On 9/26/2019 1:31 PM, Maciej Bielski wrote:
> Signed-off-by: Maciej Bielski <mba@semihalf.com>
> Acked-by: Michal Krawczyk <mk@semihalf.com>

<...>

> diff --git a/drivers/net/ena/meson.build b/drivers/net/ena/meson.build
> index 091ca6e3f..c7e71f494 100644
> --- a/drivers/net/ena/meson.build
> +++ b/drivers/net/ena/meson.build
> @@ -1,5 +1,6 @@
>  # SPDX-License-Identifier: BSD-3-Clause
> -# Copyright(c) 2018 Intel Corporation
> +# Copyright(c) 2015-2019 Amazon.com, Inc. or its affiliates.
> +# All rights reserved.
>  

This part is changing the copyright owner, it is under the ena driver but still
is there a reason to change the owner?

Overall this is a meson file, I personally don't see the meaning of having a
copyright in a meson file, but trying to be fair.

Would you mind keeping the original copyright for the file?

  parent reply	other threads:[~2019-09-26 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 12:31 Maciej Bielski
2019-09-26 15:55 ` Stephen Hemminger
2019-09-26 17:47 ` Ferruh Yigit [this message]
2019-09-27  5:32   ` Hemant Agrawal
2019-09-27  8:15     ` Michał Krawczyk
2019-09-27  8:49       ` Hemant Agrawal
2019-09-27 13:03         ` Maciej Bielski
2019-09-27  8:34     ` 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=897ca5c8-92d3-5639-7de2-484f06848868@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=evgenys@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=mba@semihalf.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.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).