From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/5] SPDX leftovers
Date: Wed, 4 Dec 2019 07:55:14 -0800 [thread overview]
Message-ID: <20191204155519.7295-1-stephen@networkplumber.org> (raw)
These are tests and scripts with missing SPDX tags.
Stephen Hemminger (5):
app/test: add SPDX tag to timer test
devtools: add license tag to cocci.sh
devtools: add SPDX tag to load-devel-config
examples/ipsecgw: add SPDX license tag
examples/performance-thread: add mising SPDX tag
app/test/test_timer_racecond.c | 34 ++-----------------
devtools/cocci.sh | 30 +---------------
devtools/load-devel-config | 2 ++
.../trs_aesgcm_inline_crypto_fallback_defs.sh | 1 +
.../tun_aesgcm_inline_crypto_fallback_defs.sh | 1 +
.../performance-thread/l3fwd-thread/test.sh | 2 ++
6 files changed, 10 insertions(+), 60 deletions(-)
--
2.20.1
next reply other threads:[~2019-12-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 15:55 Stephen Hemminger [this message]
2019-12-04 15:55 ` [dpdk-dev] [PATCH 1/5] app/test: add SPDX tag to timer test Stephen Hemminger
2019-12-04 15:55 ` [dpdk-dev] [PATCH 2/5] devtools: add license tag to cocci.sh Stephen Hemminger
2020-01-27 10:52 ` Mcnamara, John
2019-12-04 15:55 ` [dpdk-dev] [PATCH 3/5] devtools: add SPDX tag to load-devel-config Stephen Hemminger
2020-02-22 14:16 ` Thomas Monjalon
2019-12-04 15:55 ` [dpdk-dev] [PATCH 4/5] examples/ipsecgw: add SPDX license tag Stephen Hemminger
2019-12-05 20:42 ` Ananyev, Konstantin
2019-12-04 15:55 ` [dpdk-dev] [PATCH 5/5] examples/performance-thread: add mising SPDX tag Stephen Hemminger
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=20191204155519.7295-1-stephen@networkplumber.org \
--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).