From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
Olga Shern <olgas@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
"rsanford@akamai.com" <rsanford@akamai.com>,
"cchemparathy@tilera.com" <cchemparathy@tilera.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] SPDX license nag
Date: Fri, 7 Feb 2020 09:50:15 -0800 [thread overview]
Message-ID: <20200207095015.2ace054a@hermes.lan> (raw)
In-Reply-To: <MWHPR1101MB2158C7F1A0A0A2E21BDAF061FC0B0@MWHPR1101MB2158.namprd11.prod.outlook.com>
On Mon, 27 Jan 2020 11:15:44 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Stephen Hemminger
> > Sent: Wednesday, January 22, 2020 4:19 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] SPDX license nag
> >
> > Files without SPDX License
> > --------------------------
> > app/test-pmd/flowgen.c - Tilera/Mellanox
> > app/test-pmd/macswap.c - Tilera/Mellanox
> > app/test/test_compressdev_test_buffer.h - Intel
> > app/test/test_timer_racecond.c - Akamai
> > devtools/cocci.sh - EZchip/Mellanox
> > devtools/load-devel-config - Canonical
> > examples/ipsec-secgw/test/trs_aesgcm_inline_crypto_fallback_defs.sh - Intel
> > examples/ipsec-secgw/test/tun_aesgcm_inline_crypto_fallback_defs.sh - Intel
> > examples/performance-thread/l3fwd-thread/test.sh - Intel
> > lib/librte_ethdev/rte_ethdev_pci.h - Brocade/Jan Blunck/Broadcom
> > lib/librte_ethdev/rte_ethdev_vdev.h - Brocade/Jan Blunck/Broadcom
> >
> > Some patches for these are outstanding but haven't been merged
>
>
> I've looked at the headers/logs for these files and added the owners (or potential owners after mergers) above.
>
> Can everyone on the CC list please take care of these for your company/files. It is a simple patch to fix and Stephen has already provided some.
>
> Thanks Stephen for keeping the focus on this.
>
> John
>
20.02-rc2 SPDX license nag.
Files without SPDX License
--------------------------
app/test-pmd/flowgen.c
app/test-pmd/macswap.c
app/test/test_compressdev_test_buffer.h
app/test/test_timer_racecond.c
devtools/cocci.sh
devtools/load-devel-config
examples/ipsec-secgw/test/trs_aesgcm_inline_crypto_fallback_defs.sh
examples/ipsec-secgw/test/tun_aesgcm_inline_crypto_fallback_defs.sh
examples/performance-thread/l3fwd-thread/test.sh
lib/librte_ethdev/rte_ethdev_pci.h
lib/librte_ethdev/rte_ethdev_vdev.h
Files with additional license text
----------------------------------
app/test-pmd/flowgen.c
app/test-pmd/macswap.c
app/test/test_timer_racecond.c
devtools/cocci.sh
lib/librte_ethdev/rte_ethdev_pci.h
lib/librte_ethdev/rte_ethdev_vdev.h
prev parent reply other threads:[~2020-02-07 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 16:19 Stephen Hemminger
2020-01-27 11:15 ` Mcnamara, John
2020-02-07 17:50 ` Stephen Hemminger [this message]
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=20200207095015.2ace054a@hermes.lan \
--to=stephen@networkplumber.org \
--cc=ajit.khaparde@broadcom.com \
--cc=bruce.richardson@intel.com \
--cc=cchemparathy@tilera.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=olgas@mellanox.com \
--cc=rsanford@akamai.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).