DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yong Wang <yongwang@vmware.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style
Date: Thu, 12 Apr 2018 21:39:55 +0000	[thread overview]
Message-ID: <C01C5798-D225-41F0-8C10-4FCD68D2C101@vmware.com> (raw)
In-Reply-To: <1523264319-26429-1-git-send-email-hemant.agrawal@nxp.com>

On 4/9/18, 2:00 AM, "dev on behalf of Hemant Agrawal" <dev-bounces@dpdk.org on behalf of hemant.agrawal@nxp.com> wrote:

    Cc: skhare@vmware.com
    
    Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
    ---
Acked-by: Yong Wang <yongwang@vmware.com>

     drivers/net/vmxnet3/base/upt1_defs.h    | 7 ++-----
     drivers/net/vmxnet3/base/vmxnet3_defs.h | 7 ++-----
     2 files changed, 4 insertions(+), 10 deletions(-)
    
    diff --git a/drivers/net/vmxnet3/base/upt1_defs.h b/drivers/net/vmxnet3/base/upt1_defs.h
    index cf9141b..5fd7a39 100644
    --- a/drivers/net/vmxnet3/base/upt1_defs.h
    +++ b/drivers/net/vmxnet3/base/upt1_defs.h
    @@ -1,9 +1,6 @@
    -/*********************************************************
    +/* SPDX-License-Identifier: BSD-3-Clause
      * Copyright (C) 2007 VMware, Inc. All rights reserved.
    - *
    - * SPDX-License-Identifier:    BSD-3-Clause
    - *
    - *********************************************************/
    + */
     
     /* upt1_defs.h
      *
    diff --git a/drivers/net/vmxnet3/base/vmxnet3_defs.h b/drivers/net/vmxnet3/base/vmxnet3_defs.h
    index a455e27..a30b8f2 100644
    --- a/drivers/net/vmxnet3/base/vmxnet3_defs.h
    +++ b/drivers/net/vmxnet3/base/vmxnet3_defs.h
    @@ -1,9 +1,6 @@
    -/*********************************************************
    +/* SPDX-License-Identifier: BSD-3-Clause
      * Copyright (C) 2007 VMware, Inc. All rights reserved.
    - *
    - * SPDX-License-Identifier:    BSD-3-Clause
    - *
    - *********************************************************/
    + */
     
     /*
      * vmxnet3_defs.h --
    -- 
    2.7.4
    
    


  parent reply	other threads:[~2018-04-12 21:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09  8:58 Hemant Agrawal
2018-04-09  8:58 ` [dpdk-dev] [PATCH] eal: add missing SPDX identifiers Hemant Agrawal
2018-05-25  8:20   ` Thomas Monjalon
2018-04-09  8:58 ` [dpdk-dev] [PATCH] test/crypto-perf: add missing SPDX identifier Hemant Agrawal
2018-04-17 15:08   ` De Lara Guarch, Pablo
2018-04-17 15:10   ` De Lara Guarch, Pablo
2018-04-09  8:58 ` [dpdk-dev] [PATCH] usertools: " Hemant Agrawal
2018-04-09 10:24   ` Neil Horman
2018-04-10 23:50     ` Thomas Monjalon
2018-04-09  8:58 ` [dpdk-dev] [PATCH] usertools: change to SPDX license identifier Hemant Agrawal
2018-04-09  9:07   ` Jerin Jacob
2018-04-10 23:50     ` Thomas Monjalon
2018-04-09  8:58 ` [dpdk-dev] [PATCH] kernel: add missing " Hemant Agrawal
2018-04-09  8:58 ` [dpdk-dev] [PATCH] pkg: change to " Hemant Agrawal
2018-05-25  8:22   ` Thomas Monjalon
2018-04-12 21:39 ` Yong Wang [this message]
2018-04-17 17:44   ` [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style 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=C01C5798-D225-41F0-8C10-4FCD68D2C101@vmware.com \
    --to=yongwang@vmware.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).