From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: groeck@chromium.org, gwendal@chromium.org, kernel@collabora.com,
bleung@chromium.org
Subject: [PATCH 08/10] platform/chrome: cros_ec_lightbar: switch to SPDX identifier
Date: Tue, 8 Jan 2019 17:10:14 +0100 [thread overview]
Message-ID: <20190108161016.12361-9-enric.balletbo@collabora.com> (raw)
In-Reply-To: <20190108161016.12361-1-enric.balletbo@collabora.com>
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
---
drivers/platform/chrome/cros_ec_lightbar.c | 22 ++++------------------
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/platform/chrome/cros_ec_lightbar.c b/drivers/platform/chrome/cros_ec_lightbar.c
index 4211a26587d3..596b899e5508 100644
--- a/drivers/platform/chrome/cros_ec_lightbar.c
+++ b/drivers/platform/chrome/cros_ec_lightbar.c
@@ -1,21 +1,7 @@
-/*
- * cros_ec_lightbar - expose the Chromebook Pixel lightbar to userspace
- *
- * Copyright (C) 2014 Google, Inc.
- *
- * This program is free software; you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation; either version 2 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program. If not, see <http://www.gnu.org/licenses/>.
- */
+// SPDX-License-Identifier: GPL-2.0+
+// Expose the Chromebook Pixel lightbar to userspace
+//
+// Copyright (C) 2014 Google, Inc.
#include <linux/ctype.h>
#include <linux/fs.h>
--
2.20.1
next prev parent reply other threads:[~2019-01-08 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:10 [PATCH 00/10] platform/chrome: cros_ec: remove unused includes and switch to SPDX Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 01/10] platform/chrome: cros_ec_debugfs: remove unused includes Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 02/10] platform/chrome: cros_ec_lightbar: " Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 03/10] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 04/10] platform/chrome: cros_ec_vbc: " Enric Balletbo i Serra
2019-01-08 17:16 ` Guenter Roeck
2019-01-08 21:31 ` Enric Balletbo Serra
2019-01-08 16:10 ` [PATCH 05/10] platform/chrome: cros_ec_lightbar: remove pr_fmt() define Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 06/10] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 07/10] platform/chrome: cros_ec_debugfs: switch to SPDX identifier Enric Balletbo i Serra
2019-01-08 16:10 ` Enric Balletbo i Serra [this message]
2019-01-08 16:10 ` [PATCH 09/10] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-08 16:10 ` [PATCH 10/10] platform/chrome: cros_ec_vbc: " Enric Balletbo i Serra
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=20190108161016.12361-9-enric.balletbo@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.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).