From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 8/8] doc: add SPDX tag for Intel copyright file
Date: Tue, 19 Dec 2017 15:49:06 +0000 [thread overview]
Message-ID: <20171219154906.227759-9-bruce.richardson@intel.com> (raw)
In-Reply-To: <20171219154906.227759-1-bruce.richardson@intel.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/guides/conf.py | 31 ++-----------------------------
1 file changed, 2 insertions(+), 29 deletions(-)
diff --git a/doc/guides/conf.py b/doc/guides/conf.py
index 31f914a89..77d93acf1 100644
--- a/doc/guides/conf.py
+++ b/doc/guides/conf.py
@@ -1,32 +1,5 @@
-# BSD LICENSE
-# Copyright(c) 2010-2015 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.
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2010-2015 Intel Corporation
from __future__ import print_function
import subprocess
--
2.14.3
next prev parent reply other threads:[~2017-12-19 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:48 [dpdk-dev] [PATCH 0/8] replace BSD headers with SPDX tags Bruce Richardson
2017-12-19 15:48 ` [dpdk-dev] [PATCH 1/8] app: add SPDX tags for Intel copyright Makefiles Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 2/8] tools: add SPDX tags for Intel copyright scripts Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 3/8] drivers: add SPDX tags for Intel copyright Makefiles Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 4/8] examples: " Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 5/8] lib: " Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 6/8] mk: " Bruce Richardson
2017-12-19 15:49 ` [dpdk-dev] [PATCH 7/8] test: " Bruce Richardson
2017-12-19 15:49 ` Bruce Richardson [this message]
2017-12-19 16:02 ` [dpdk-dev] [PATCH 0/8] replace BSD headers with SPDX tags Stephen Hemminger
2018-01-04 21:11 ` Thomas Monjalon
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=20171219154906.227759-9-bruce.richardson@intel.com \
--to=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).