From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: [net-next 02/13] Documentation: e100, e1000: Add missing SPDX header
Date: Thu, 18 Oct 2018 13:32:48 -0700 [thread overview]
Message-ID: <20181018203259.4175-3-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <20181018203259.4175-1-jeffrey.t.kirsher@intel.com>
Add the SPDX-Lincense-Identifier to the Intel wired Ethernet *.rst
kernel documentation.
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
---
Documentation/networking/e100.rst | 3 ++-
Documentation/networking/e1000.rst | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/e100.rst b/Documentation/networking/e100.rst
index f81111eba9c5..5e2839b4ec92 100644
--- a/Documentation/networking/e100.rst
+++ b/Documentation/networking/e100.rst
@@ -1,4 +1,5 @@
-==============================================================
+.. SPDX-License-Identifier: GPL-2.0+
+
Linux* Base Driver for the Intel(R) PRO/100 Family of Adapters
==============================================================
diff --git a/Documentation/networking/e1000.rst b/Documentation/networking/e1000.rst
index f10dd4086921..6379d4d20771 100644
--- a/Documentation/networking/e1000.rst
+++ b/Documentation/networking/e1000.rst
@@ -1,4 +1,5 @@
-===========================================================
+.. SPDX-License-Identifier: GPL-2.0+
+
Linux* Base Driver for Intel(R) Ethernet Network Connection
===========================================================
--
2.17.2
next prev parent reply other threads:[~2018-10-19 4:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 20:32 [net-next 00/13][pull request] Intel Wired LAN Doc Updates 2018-10-18 Jeff Kirsher
2018-10-18 20:32 ` [net-next 01/13] Documentation: networking: ixgb: Remove reference to IXGB_NAPI Jeff Kirsher
2018-10-18 20:32 ` Jeff Kirsher [this message]
2018-10-18 20:32 ` [net-next 03/13] Documentation: ixgb: Prepare documentation for RST conversion Jeff Kirsher
2018-10-18 20:32 ` [net-next 04/13] Documentation: e1000e: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 05/13] Documentation: igb: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 06/13] Documentation: igbvf: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 07/13] Documentation: ixgbe: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 08/13] Documentation: ixgbevf: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 09/13] Documentation: i40e: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 10/13] Documentation: iavf: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 11/13] Documentation: ice: " Jeff Kirsher
2018-10-18 20:32 ` [net-next 12/13] Documentation: fm10k: Add kernel documentation Jeff Kirsher
2018-10-18 20:32 ` [net-next 13/13] Documentation: intel: Convert to RST format Jeff Kirsher
2018-10-18 22:46 ` [net-next 00/13][pull request] Intel Wired LAN Doc Updates 2018-10-18 David Miller
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=20181018203259.4175-3-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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