From: tedd.an@linux.intel.com
To: linux-bluetooth@vger.kernel.org
Cc: Tedd Ho-Jeong An <tedd.an@intel.com>
Subject: [BlueZ 03/17] btio: Add SPDX License Identifier
Date: Fri, 11 Sep 2020 23:23:43 -0700 [thread overview]
Message-ID: <20200912062357.23926-4-tedd.an@linux.intel.com> (raw)
In-Reply-To: <20200912062357.23926-1-tedd.an@linux.intel.com>
From: Tedd Ho-Jeong An <tedd.an@intel.com>
This patch adds SPDX License Identifier.
-------------------------------------
License COUNT
-------------------------------------
GPL-2.0-or-later : 2
License: GPL-2.0-or-later
btio/btio.h
btio/btio.c
---
btio/btio.c | 1 +
btio/btio.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/btio/btio.c b/btio/btio.c
index 844d6007f..42874e13c 100644
--- a/btio/btio.c
+++ b/btio/btio.c
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
/*
*
* BlueZ - Bluetooth protocol stack for Linux
diff --git a/btio/btio.h b/btio/btio.h
index 23e0ef72b..e15f52a7c 100644
--- a/btio/btio.h
+++ b/btio/btio.h
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
/*
*
* BlueZ - Bluetooth protocol stack for Linux
--
2.25.4
next parent reply other threads:[~2020-09-12 6:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200912062357.23926-1-tedd.an@linux.intel.com>
2020-09-12 6:23 ` tedd.an [this message]
2020-09-12 6:51 ` [BlueZ,03/17] btio: Add SPDX License Identifier bluez.test.bot
2020-09-12 6:23 ` [BlueZ 04/17] client: Add SPDX License Identifer tedd.an
2020-09-12 6:51 ` [BlueZ,04/17] " bluez.test.bot
2020-09-12 6:23 ` [BlueZ 05/17] emulator: Add SPDX License Identifier tedd.an
2020-09-12 6:51 ` [BlueZ,05/17] " bluez.test.bot
2020-09-12 6:23 ` [BlueZ 11/17] obexd: Add SPDX License Identifer tedd.an
2020-09-12 6:51 ` [BlueZ,11/17] " bluez.test.bot
2020-09-12 6:23 ` [BlueZ 13/17] plugins: " tedd.an
2020-09-14 17:32 ` Luiz Augusto von Dentz
2020-09-14 20:26 ` An, Tedd
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=20200912062357.23926-4-tedd.an@linux.intel.com \
--to=tedd.an@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tedd.an@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).