From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 3/5] devtools: add SPDX tag to load-devel-config
Date: Wed, 4 Dec 2019 07:55:17 -0800 [thread overview]
Message-ID: <20191204155519.7295-4-stephen@networkplumber.org> (raw)
In-Reply-To: <20191204155519.7295-1-stephen@networkplumber.org>
Trivial file was missing any license.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
devtools/load-devel-config | 2 ++
1 file changed, 2 insertions(+)
diff --git a/devtools/load-devel-config b/devtools/load-devel-config
index 380c79db41eb..ca1bc21b55e3 100644
--- a/devtools/load-devel-config
+++ b/devtools/load-devel-config
@@ -1,3 +1,5 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# This file is intended to be sourced into shell
# Load DPDK devel config and allow override
# from system file
test ! -r /etc/dpdk/devel.config ||
--
2.20.1
next prev parent 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 [dpdk-dev] [PATCH 0/5] SPDX leftovers Stephen Hemminger
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 ` Stephen Hemminger [this message]
2020-02-22 14:16 ` [dpdk-dev] [PATCH 3/5] devtools: add SPDX tag to load-devel-config 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-4-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.