From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH 00/17] use SPDX tags on 6WIND copyrighted files
Date: Tue, 30 Jan 2018 19:36:30 +0530 [thread overview]
Message-ID: <d1d412c8-96a4-35bd-8aae-de35949b393b@nxp.com> (raw)
In-Reply-To: <20180129131136.25863-1-olivier.matz@6wind.com>
On 1/29/2018 6:41 PM, Olivier Matz wrote:
> This patchset updates the license on files that contain a 6WIND copyright
> to use a SPDX tag.
> It applies on master + https://dpdk.org/dev/patchwork/patch/34604/
>
> For components I am maintaining (mempool, mbuf, cmdline, kvargs, net), I
> update all the *.[ch] files. For the other components, I only update
> files where there is a 6WIND copyright.
>
> The change is done automatically: the copyrights stay as is, except:
> - standardisation of the text for 6WIND copyright
> - as discussed with Bruce, Thomas, and Ferruh, the "All rights reserved"
> mention is removed if the copyright are from 6WIND, Intel or Mellanox.
>
> For each patch, the maintainers are Cc'd.
The series LGTM.
Bruce/Ferruh, please ack it from Intel side.
Thomas, you may ack it from Mellanox side or someelse can ack the
relevant patches form Mellanox side.
Regards,
Hemant
next prev parent reply other threads:[~2018-01-30 14:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 13:11 Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 01/17] cmdline: use SPDX tags Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 02/17] mbuf: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 03/17] mempool: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 04/17] kvargs: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 05/17] net: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 06/17] eal: use SPDX tags on 6WIND copyrighted files Olivier Matz
2018-01-29 16:45 ` Ananyev, Konstantin
2018-01-29 13:11 ` [dpdk-dev] [PATCH 07/17] ethdev: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 08/17] pci: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 09/17] app/testpmd: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 10/17] test: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 11/17] net/mlx5: " Olivier Matz
2018-01-30 9:19 ` Nélio Laranjeiro
2018-01-29 13:11 ` [dpdk-dev] [PATCH 12/17] net/mlx4: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 13/17] bus/pci: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 14/17] net/af_packet: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 15/17] net/failsafe: " Olivier Matz
2018-01-29 13:11 ` [dpdk-dev] [PATCH 16/17] net/ixgbe: " Olivier Matz
2018-01-29 16:46 ` Ananyev, Konstantin
2018-01-29 13:11 ` [dpdk-dev] [PATCH 17/17] net/tap: " Olivier Matz
2018-01-30 14:06 ` Hemant Agrawal [this message]
2018-01-30 15:08 ` [dpdk-dev] [PATCH 00/17] " Bruce Richardson
2018-02-01 1:28 ` 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=d1d412c8-96a4-35bd-8aae-de35949b393b@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.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).