DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Allain Legacy <allain.legacy@windriver.com>,
	Matt Peters <matt.peters@windriver.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>, dev <dev@dpdk.org>,
	 "Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	 Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] test: replace license text with SPDX tag
Date: Mon, 14 Oct 2019 20:51:38 +0200	[thread overview]
Message-ID: <CAJFAV8w+HLAY-p0X8Y4weqSsi+HeCrZ9ccrsL6qvQk-yRkKeQQ@mail.gmail.com> (raw)
In-Reply-To: <20190813122013.14070-1-allain.legacy@windriver.com>

On Tue, Aug 13, 2019 at 2:20 PM Allain Legacy
<allain.legacy@windriver.com> wrote:
>
> Replacing full license text with SPDX tag.
>
> Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
> ---
>  app/test/test_cfgfile.c | 32 ++------------------------------
>  1 file changed, 2 insertions(+), 30 deletions(-)
>
> diff --git a/app/test/test_cfgfile.c b/app/test/test_cfgfile.c
> index 37435b395..01905920e 100644
> --- a/app/test/test_cfgfile.c
> +++ b/app/test/test_cfgfile.c
> @@ -1,33 +1,5 @@
> -/*-
> - *   BSD LICENSE
> - *
> - *   Copyright(c) 2017 Wind River Systems Inc. All rights reserved.
> - *
> - *   Redistribution and use in source and binary forms, with or without
> - *   modification, are permitted provided that the following conditions
> - *   are met:
> - *
> - *     * Redistributions of source code must retain the above copyright
> - *       notice, this list of conditions and the following disclaimer.
> - *     * Redistributions in binary form must reproduce the above copyright
> - *       notice, this list of conditions and the following disclaimer in
> - *       the documentation and/or other materials provided with the
> - *       distribution.
> - *     * Neither the name of Intel Corporation nor the names of its
> - *       contributors may be used to endorse or promote products derived
> - *       from this software without specific prior written permission.
> - *
> - *   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> - *   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> - *   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> - *   A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
> - *   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> - *   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> - *   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> - *   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> - *   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> - *   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> - *   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright(c) 2017 Wind River Systems Inc. All rights reserved.

Once applied the two patches of this series, we end up with 3 kind of
copyright lines:

$ git grep -h Copyright.*Wind.River app/
 * Copyright(c) 2017 Wind River Systems Inc. All rights reserved.

$ git grep -h Copyright.*Wind.River doc/
    Copyright(c) 2017 Wind River Systems, Inc. rights reserved.

$ git grep -h Copyright.*Wind.River drivers/
# Copyright(c) 2013-2017, Wind River Systems, Inc.
 * Copyright(c) 2013-2017 Wind River Systems, Inc.
 * Copyright(c) 2013-2017 Wind River Systems, Inc.
 * Copyright(c) 2014-2017 Wind River Systems, Inc.
 * Copyright(c) 2013-2017 Wind River Systems, Inc.

Should I still apply them as is? or do you want to send a v2?


Thanks.
-- 
David Marchand


  parent reply	other threads:[~2019-10-14 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 12:20 Allain Legacy
2019-08-13 12:20 ` [dpdk-dev] [PATCH 2/2] doc: " Allain Legacy
2019-08-14  8:40   ` Hemant Agrawal
2019-08-14 12:18   ` Peters, Matt
2019-08-14  8:39 ` [dpdk-dev] [PATCH 1/2] test: " Hemant Agrawal
2019-08-14 12:17 ` Peters, Matt
2019-10-14 18:51 ` David Marchand [this message]
2019-11-07 20:37 Allain Legacy
2019-11-08  4:00 ` Stephen Hemminger
2019-11-28  2:07   ` 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=CAJFAV8w+HLAY-p0X8Y4weqSsi+HeCrZ9ccrsL6qvQk-yRkKeQQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=allain.legacy@windriver.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=matt.peters@windriver.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).