From: ohilyard@iol.unh.edu
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [PATCH] framework/flow: Add license and copyright
Date: Wed, 12 Jan 2022 11:44:48 -0500 [thread overview]
Message-ID: <20220112164448.30409-1-ohilyard@iol.unh.edu> (raw)
From: Owen Hilyard <ohilyard@iol.unh.edu>
Add SPDX license and copyright to module file.
Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
---
framework/flow/__init__.py | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/framework/flow/__init__.py b/framework/flow/__init__.py
index e69de29b..4124376e 100644
--- a/framework/flow/__init__.py
+++ b/framework/flow/__init__.py
@@ -0,0 +1,4 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2021- University of New Hampshire
+
+# Empty file required for python imports to work correctly
\ No newline at end of file
--
2.30.2
next reply other threads:[~2022-01-12 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:44 ohilyard [this message]
2022-01-14 7:28 ` Tu, Lijuan
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=20220112164448.30409-1-ohilyard@iol.unh.edu \
--to=ohilyard@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
/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).