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 v3 08/12] platform/chrome: cros_ec_proto: switch to SPDX identifier
Date: Tue, 29 Jan 2019 10:38:19 +0100 [thread overview]
Message-ID: <20190129093823.27137-9-enric.balletbo@collabora.com> (raw)
In-Reply-To: <20190129093823.27137-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>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_proto.c | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/drivers/platform/chrome/cros_ec_proto.c b/drivers/platform/chrome/cros_ec_proto.c
index d2ba662fc713..d259ff264e9d 100644
--- a/drivers/platform/chrome/cros_ec_proto.c
+++ b/drivers/platform/chrome/cros_ec_proto.c
@@ -1,18 +1,7 @@
-/*
- * ChromeOS EC communication protocol helper functions
- *
- * Copyright (C) 2015 Google, Inc
- *
- * This software is licensed under the terms of the GNU General Public
- * License version 2, as published by the Free Software Foundation, and
- * may be copied, distributed, and modified under those terms.
- *
- * 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.
- *
- */
+// SPDX-License-Identifier: GPL-2.0
+// ChromeOS EC communication protocol helper functions
+//
+// Copyright (C) 2015 Google, Inc
#include <linux/mfd/cros_ec.h>
#include <linux/delay.h>
--
2.20.1
next prev parent reply other threads:[~2019-01-29 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 9:38 [PATCH v3 00/12] platform/chrome: switch to SPDX license and some minor cleanup Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 01/12] platform/chrome: cromeos_pstore: switch to SPDX identifier Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 02/12] platform/chrome: cros_ec_debugfs: " Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 03/12] platform/chrome: cros_ec_lightbar: " Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 04/12] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 05/12] platform/chrome: cros_ec_vbc: " Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 06/12] platform/chrome: cros_ec_i2c: " Enric Balletbo i Serra
2019-01-29 14:42 ` Guenter Roeck
2019-01-29 9:38 ` [PATCH v3 07/12] platform/chrome: cros_ec_lpc: " Enric Balletbo i Serra
2019-01-29 9:38 ` Enric Balletbo i Serra [this message]
2019-01-29 9:38 ` [PATCH v3 09/12] platform/chrome: cros_ec_spi: " Enric Balletbo i Serra
2019-01-29 14:43 ` Guenter Roeck
2019-01-29 9:38 ` [PATCH v3 10/12] platform/chrome: cros_kbd_led_backlight: " Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 11/12] platform/chrome: cros_ec_lightbar: remove pr_fmt() define Enric Balletbo i Serra
2019-01-29 9:38 ` [PATCH v3 12/12] platform/chrome: cros_ec_sysfs: " 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=20190129093823.27137-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).