DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Hemant <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] net/bnx2x: move SPDX tags to source files
Date: Mon, 16 Jul 2018 20:05:05 +0000	[thread overview]
Message-ID: <SN1PR07MB4032084C683BB6CCEFCFD1EF9F5D0@SN1PR07MB4032.namprd07.prod.outlook.com> (raw)
In-Reply-To: <a805bfc7-f605-4e06-3b98-89ee951866a0@nxp.com>

Hi Hemant,
> From: Hemant [mailto:hemant.agrawal@nxp.com]
> Sent: Sunday, July 15, 2018 11:30 PM
> 
> Hi Rasesh
> 
> On 7/14/2018 7:03 AM, Rasesh Mody wrote:
> > diff --git a/drivers/net/bnx2x/bnx2x_stats.h
> > b/drivers/net/bnx2x/bnx2x_stats.h index 6fcaf60..107ef20 100644
> > --- a/drivers/net/bnx2x/bnx2x_stats.h
> > +++ b/drivers/net/bnx2x/bnx2x_stats.h
> > @@ -1,4 +1,4 @@
> > -/*-
> > +/* SPDX-License-Identifier: BSD-3-Clause
> >    * Copyright (c) 2007-2013 Cavium Inc. All rights reserved.
> >    *
> >    * Eric Davis        <edavis@broadcom.com>
> > @@ -9,8 +9,6 @@
> >    * Copyright (c) 2015-2018 Cavium Inc.
> >    * All rights reserved.
> >    * www.cavium.com
> > - *
> > - * See LICENSE.bnx2x_pmd for copyright and licensing details.
> >    */
> >
> >
> I see that some of the files have the Cavium copyright two times (like above).
> you may want to clean it in future patch.

We'll clean it up.

Thanks!
-Rasesh
 
> 
> 
>   Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

  reply	other threads:[~2018-07-16 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08  5:24 [dpdk-dev] [PATCH] " Rasesh Mody
2018-07-09 21:07 ` Thomas Monjalon
2018-07-10 15:57   ` Mody, Rasesh
2018-07-14  1:33 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2018-07-16  6:29   ` Hemant
2018-07-16 20:05     ` Mody, Rasesh [this message]
2018-07-27 15:47   ` [dpdk-dev] [PATCH v3] " Rasesh Mody
2018-08-03 14:48     ` 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=SN1PR07MB4032084C683BB6CCEFCFD1EF9F5D0@SN1PR07MB4032.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=thomas@monjalon.net \
    /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).