From: Chen Linglix <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: Chen Linglix <linglix.chen@intel.com>
Subject: [dts] [dts 10/10] tools/setup.py:add the BSD License header information
Date: Tue, 13 Oct 2020 15:07:14 +0000 [thread overview]
Message-ID: <20201013150714.3258960-11-linglix.chen@intel.com> (raw)
In-Reply-To: <20201013150714.3258960-1-linglix.chen@intel.com>
Signed-off-by: Chen Linglix <linglix.chen@intel.com>
---
tools/setup.py | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/tools/setup.py b/tools/setup.py
index c0852f21..983209c8 100755
--- a/tools/setup.py
+++ b/tools/setup.py
@@ -1,3 +1,34 @@
+# BSD LICENSE
+#
+# Copyright(c) 2020 Intel Corporation. All rights reserved.
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions
+# are met:
+#
+# * Redistributions of source code must retain the above copyright
+# notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright
+# notice, this list of conditions and the following disclaimer in
+# the documentation and/or other materials provided with the
+# distribution.
+# * Neither the name of Intel Corporation nor the names of its
+# contributors may be used to endorse or promote products derived
+# from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
import sys
import os
import parse_opt
--
2.17.1
next prev parent reply other threads:[~2020-10-13 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 15:07 [dts] [PATCH V1 00/10] add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 01/10] framework/test_capabilities.py:add " Chen Linglix
2020-10-22 0:53 ` Tu, Lijuan
2020-10-13 15:07 ` [dts] [dts 02/10] framework/texttable.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 03/10] framework/ssh_pexpect.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 04/10] framework/checkCase.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 05/10] framework/multiple_vm.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 06/10] framework/exception.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 07/10] framework/crbs.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 08/10] tools/dump_case.py:add " Chen Linglix
2020-10-13 15:07 ` [dts] [dts 09/10] tools/parse_opt.py:add " Chen Linglix
2020-10-13 15:07 ` Chen Linglix [this message]
2020-10-16 5:25 ` [dts] [dts 10/10] tools/setup.py:add " Ma, LihongX
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=20201013150714.3258960-11-linglix.chen@intel.com \
--to=linglix.chen@intel.com \
--cc=dts@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).