DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnx2x: move SPDX tags to source files
Date: Tue, 10 Jul 2018 15:57:38 +0000	[thread overview]
Message-ID: <SN1PR07MB40328B4852E70DB40694AF0C9F5B0@SN1PR07MB4032.namprd07.prod.outlook.com> (raw)
In-Reply-To: <6990726.I9aQltfJUb@xps>

> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, July 09, 2018 2:07 PM
> 
> Hi,
> 
> 08/07/2018 07:24, Rasesh Mody:
> > We were using LICENSE.bnx2x_pmd to reference inclusion of SPDX
> > licensing tag from all the source file. Remove the LICENSE.bnx2x_pmd
> > file and directly include SPDX tags in source files.
> >
> > Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
> > --- a/drivers/net/bnx2x/Makefile
> > +++ b/drivers/net/bnx2x/Makefile
> > @@ -2,7 +2,7 @@
> >  #    All rights reserved.
> >  #    www.cavium.com
> >  #
> > -#    See LICENSE.bnx2x_pmd for copyright and licensing details.
> > +#    SPDX-License-Identifier: BSD-3-Clause
> 
> The SPDX line should be the first line.

I will send a v2 with the change.

Thanks!
-Rasesh
> 
> You can take a look at doc/guides/contributing/patches.rst
> 
> Thanks
> 

  reply	other threads:[~2018-07-10 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08  5:24 Rasesh Mody
2018-07-09 21:07 ` Thomas Monjalon
2018-07-10 15:57   ` Mody, Rasesh [this message]
2018-07-14  1:33 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2018-07-16  6:29   ` Hemant
2018-07-16 20:05     ` Mody, Rasesh
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=SN1PR07MB40328B4852E70DB40694AF0C9F5B0@SN1PR07MB4032.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Dept-EngDPDKDev@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).