From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] 20.11-rc SPDX compliance report
Date: Mon, 16 Nov 2020 09:16:10 +0000 [thread overview]
Message-ID: <b4edb11b-0725-49b7-f7c6-875e4b29998e@intel.com> (raw)
In-Reply-To: <20201115140818.34269648@hermes.local>
On 11/15/2020 10:08 PM, Stephen Hemminger wrote:
> Current output of check-spdx-tag.sh
>
> Files without SPDX License
> --------------------------
> doc/guides/custom.css
> doc/guides/linux_gsg/nic_perf_intel_platform.rst
> drivers/net/iavf/rte_pmd_iavf.h
'rte_pmd_iavf.h' has SPDX license but there is typo in it, I will send a quick
patch for it.
> examples/multi_process/Makefile
> examples/multi_process/client_server_mp/Makefile
> lib/librte_eal/windows/eal_hugepages.c
>
>
> Files with redundant license text
> ---------------------------------
> app/test/test_timer_racecond.c
>
> total: 6 errors, 1 warnings
>
prev parent reply other threads:[~2020-11-16 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 22:08 Stephen Hemminger
2020-11-16 9:16 ` Ferruh Yigit [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=b4edb11b-0725-49b7-f7c6-875e4b29998e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).