From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] SPDX open issues
Date: Sat, 27 Feb 2021 11:13:18 -0800 [thread overview]
Message-ID: <20210227111318.6b031cd0@hermes.local> (raw)
Current SPDX issues in main branch. Thomas we should run this
before every release.
$ ./devtools/check-spdx-tag.sh -v
Files without SPDX License
--------------------------
app/test-crypto-perf/configs/crypto-perf-aesni-gcm.json
app/test-crypto-perf/configs/crypto-perf-aesni-mb.json
app/test-crypto-perf/configs/crypto-perf-qat.json
doc/guides/custom.css
drivers/common/mlx5/windows/mlx5_win_defs.h
drivers/common/mlx5/windows/mlx5_win_ext.h
lib/librte_eal/windows/eal_hugepages.c
Files with redundant license text
---------------------------------
app/test/test_timer_racecond.c
total: 7 errors, 1 warnings
reply other threads:[~2021-02-27 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210227111318.6b031cd0@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).