From: Stephen Hemminger <stephen@networkplumber.org>
To: bruce.richardson@intel.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] examples/multi_process: add missing SPDX header to Makefile
Date: Sun, 15 Nov 2020 18:23:47 -0800 [thread overview]
Message-ID: <20201116022347.26136-1-stephen@networkplumber.org> (raw)
Make is still used for these examples, so add header to Makefile
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
examples/multi_process/Makefile | 3 +++
examples/multi_process/client_server_mp/Makefile | 3 +++
2 files changed, 6 insertions(+)
diff --git a/examples/multi_process/Makefile b/examples/multi_process/Makefile
index f0a999745a7d..937d00faa313 100644
--- a/examples/multi_process/Makefile
+++ b/examples/multi_process/Makefile
@@ -1,3 +1,6 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2010-2014 Intel Corporation
+
subdirs := client_server_mp hotplug_mp simple_mp symmetric_mp
.PHONY: all static shared clean $(subdirs)
diff --git a/examples/multi_process/client_server_mp/Makefile b/examples/multi_process/client_server_mp/Makefile
index e8debdfd9ac7..fbe6d67a7771 100644
--- a/examples/multi_process/client_server_mp/Makefile
+++ b/examples/multi_process/client_server_mp/Makefile
@@ -1,3 +1,6 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2010-2014 Intel Corporation
+
subdirs := mp_client mp_server
.PHONY: all static shared clean $(subdirs)
--
2.27.0
next reply other threads:[~2020-11-16 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 2:23 Stephen Hemminger [this message]
2020-11-16 9:27 ` Bruce Richardson
2020-11-16 9:33 ` [dpdk-dev] [PATCH v2] examples/multi_process: fix missing SPDX headers Bruce Richardson
2020-11-20 16:34 ` David Marchand
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=20201116022347.26136-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--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).