mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	Gwendal Grignou <gwendal@chromium.org>,
	kernel@collabora.com
Subject: Re: [PATCH v2 3/8] mfd: cros_ec: Add or fix SPDX-License-Identifier in all files.
Date: Tue, 19 Jun 2018 11:05:05 +0200	[thread overview]
Message-ID: <0ab6b76e-11b3-dc1e-bd14-af69d7dd6a8d@collabora.com> (raw)
In-Reply-To: <20180618063750.GH31141@dell>

Hi Lee,

On 18/06/18 08:37, Lee Jones wrote:
> On Tue, 05 Jun 2018, Enric Balletbo i Serra wrote:
> 
>> And get rid of the license text that is no longer necessary. Also fix
>> the license as sometimes doesn't match what the header with the value in
>> the MODULE_LICENSE macro. Assuming that the desired license is GPL-2.0+,
>> all the files are updated to this license version.
>>
>> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>> ---
>>
>> Changes in v2: None
>>
>>  drivers/mfd/cros_ec.c                | 26 ++++++++------------------
>>  drivers/mfd/cros_ec_dev.c            | 23 +++++------------------
>>  drivers/mfd/cros_ec_dev.h            | 16 ++--------------
>>  drivers/mfd/cros_ec_i2c.c            | 18 ++++--------------
>>  drivers/mfd/cros_ec_spi.c            | 20 +++++---------------
>>  include/linux/mfd/cros_ec.h          | 10 +---------
>>  include/linux/mfd/cros_ec_commands.h | 10 +---------
>>  include/linux/mfd/cros_ec_lpc_mec.h  | 14 +++-----------
>>  include/linux/mfd/cros_ec_lpc_reg.h  | 14 +++-----------
>>  9 files changed, 32 insertions(+), 119 deletions(-)
>>
>> diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c
>> index 58e05069163e..5b6a1c541543 100644
>> --- a/drivers/mfd/cros_ec.c
>> +++ b/drivers/mfd/cros_ec.c
>> @@ -1,21 +1,11 @@
>> -/*
>> - * ChromeOS EC multi-function device
>> - *
>> - * Copyright (C) 2012 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.
>> - *
>> - * The ChromeOS EC multi function device is used to mux all the requests
>> - * to the EC device for its multiple features: keyboard controller,
>> - * battery charging and regulator control, firmware update.
>> - */
>> +// SPDX-License-Identifier: GPL-2.0+
>> +// ChromeOS EC multi-function device.
>> +//
>> +// Copyright (C) 2012 Google, Inc
>> +//
>> +// The ChromeOS EC multi function device is used to mux all the requests
>> +// to the EC device for its multiple features: keyboard controller,
>> +// battery charging and regulator control, firmware update.
> 
> I must admit I haven't seen a great many patches like this.  Is C++
> comments for the SPDX header *and* the Copyright text the done thing
> now then?
> 

There is a bit of mess here, as per documentation, it is clear that the SPDX tag
for .c files should go in C++ style, but for the copyright notice is not clear
and there are differences between subsystems.

Seems that putting everything as // is Linus Torvalds' preferred style [1] but
other maintainers want the copyright in c-style. If you see current status in
the kernel both styles are present.

[1] https://lkml.org/lkml/2017/11/25/133

Best regards,
 Enric









  reply	other threads:[~2018-06-19  9:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 17:54 [PATCH v2 0/8] cros_ec: Switch to SPDX identifier Enric Balletbo i Serra
2018-06-05 17:54 ` [PATCH v2 1/8] platform/chrome: " Enric Balletbo i Serra
2018-06-05 20:51   ` Benson Leung
2018-06-05 17:54 ` [PATCH v2 2/8] platform/chrome: pstore: " Enric Balletbo i Serra
2018-06-05 20:54   ` Benson Leung
2018-06-05 17:54 ` [PATCH v2 3/8] mfd: cros_ec: Add or fix SPDX-License-Identifier in all files Enric Balletbo i Serra
2018-06-18  6:37   ` Lee Jones
2018-06-19  9:05     ` Enric Balletbo i Serra [this message]
2018-06-05 17:54 ` [PATCH v2 4/8] iio: cros_ec: Switch to SPDX identifier Enric Balletbo i Serra
2018-06-05 17:54 ` [PATCH v2 5/8] Input: cros_ec_keyb - " Enric Balletbo i Serra
2018-06-05 18:04   ` Fabio Estevam
2018-06-05 18:14     ` Enric Balletbo i Serra
2018-06-05 18:16       ` Fabio Estevam
2018-06-05 18:29         ` Dmitry Torokhov
2018-06-05 18:45           ` Enric Balletbo i Serra
2018-06-05 18:52             ` Dmitry Torokhov
2018-06-25  1:57       ` Greg KH
2018-06-25  6:23         ` Enric Balletbo i Serra
2018-06-25  6:42           ` Greg KH
2018-06-05 17:54 ` [PATCH v2 6/8] pwm: cros-ec: " Enric Balletbo i Serra
2018-06-06  9:08   ` Thierry Reding
2018-06-06  9:21     ` Enric Balletbo i Serra
2018-06-06  9:43       ` Thierry Reding
2018-07-09 17:02   ` Thierry Reding
2018-06-05 17:54 ` [PATCH v2 7/8] extcon: usbc-cros-ec: " Enric Balletbo i Serra
2018-06-05 18:15   ` Benson Leung
2018-06-05 18:43     ` Dmitry Torokhov
2018-06-05 17:54 ` [PATCH v2 8/8] i2c: i2c-cros-ec-tunnel: " 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=0ab6b76e-11b3-dc1e-bd14-af69d7dd6a8d@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=gwendal@chromium.org \
    --cc=kernel@collabora.com \
    --cc=lee.jones@linaro.org \
    --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

all inboxes | Powered by JetHome®