From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 1/3] eal/windows: add missing SPDX license tag
Date: Tue, 14 Jul 2020 16:50:09 -0700 [thread overview]
Message-ID: <20200714235011.4366-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20200714235011.4366-1-stephen@networkplumber.org>
This file was added without license information.
Add BSD SPDX license with copyright assigned to the original
author (as was done for other files in Windows EAL).
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/librte_eal/windows/eal_hugepages.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/librte_eal/windows/eal_hugepages.c b/lib/librte_eal/windows/eal_hugepages.c
index 44dae985e5d3..83a3d0ffc66c 100644
--- a/lib/librte_eal/windows/eal_hugepages.c
+++ b/lib/librte_eal/windows/eal_hugepages.c
@@ -1,3 +1,7 @@
+/* SPDX-License-Identifier: BSD-3-Clause
+ * Copyright (c) 2020 Dmitry Kozlyuk
+ */
+
#include <rte_errno.h>
#include <rte_log.h>
#include <rte_memory.h>
--
2.27.0
next prev parent reply other threads:[~2020-07-14 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 23:50 [dpdk-dev] [PATCH 0/3] Add missing SPDX license tags Stephen Hemminger
2020-07-14 23:50 ` Stephen Hemminger [this message]
2020-07-30 22:15 ` [dpdk-dev] [PATCH 1/3] eal/windows: add missing SPDX license tag Thomas Monjalon
2020-07-30 22:40 ` Dmitry Kozlyuk
2020-07-14 23:50 ` [dpdk-dev] [PATCH 2/3] net/qede/base: add missing license information Stephen Hemminger
2020-07-30 22:14 ` Thomas Monjalon
2020-07-14 23:50 ` [dpdk-dev] [PATCH 3/3] doc: add missing SPDX license tags Stephen Hemminger
2020-07-17 13:02 ` Bruce Richardson
2020-08-12 0:49 ` [dpdk-dev] [PATCH 0/3] Add " 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=20200714235011.4366-2-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.