From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: mchehab@kernel.org, shuah@kernel.org,
sakari.ailus@linux.intel.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: v4l2-core: v4l2-mc: Add SPDX license identifier
Date: Thu, 11 Jan 2018 20:42:04 +0200 [thread overview]
Message-ID: <1730571.xFN9zJKHcq@avalon> (raw)
In-Reply-To: <9e7fdf1e-64f5-093a-e1ad-a64653791429@osg.samsung.com>
Hi Shuah,
On Thursday, 11 January 2018 17:45:15 EET Shuah Khan wrote:
> On 01/11/2018 05:55 AM, Laurent Pinchart wrote:
> > On Wednesday, 10 January 2018 18:35:36 EET Shuah Khan wrote:
> >> Replace GPL license statement with SPDX GPL-2.0 license identifier.
> >>
> >> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> >> ---
> >>
> >> drivers/media/v4l2-core/v4l2-mc.c | 11 +----------
> >> 1 file changed, 1 insertion(+), 10 deletions(-)
> >>
> >> diff --git a/drivers/media/v4l2-core/v4l2-mc.c
> >> b/drivers/media/v4l2-core/v4l2-mc.c index 303980b71aae..1297132acd4e
> >> 100644
> >> --- a/drivers/media/v4l2-core/v4l2-mc.c
> >> +++ b/drivers/media/v4l2-core/v4l2-mc.c
> >> @@ -1,3 +1,4 @@
> >> +/* SPDX-License-Identifier: GPL-2.0 */
> >
> > The header doesn't match the existing license.
>
> When I added the file, I must have cut and pasted the license statement
> from another file. More on this below the deleted license lines.
>
> > Furthermore, unless I'm mistaken, the standard comment style for SPDX
> > headers in the kernel is //, not /* ... */
>
> Looks like we have 3 conventions for SPDX comment style.
> /* ... */ for headers and # ... for shell scripts and
> // for .c files.
>
> I can update it it and send v2 provided we think the change is inline
> with the original license.
Personally I prefer the /* ... */ comment style, but I noticed that Greg used
// in his large patch the adds SPDX license headers, so I think we should
follow the established practice. I'll let you investigate to find what is
preferred :)
> >> /*
> >>
> >> * Media Controller ancillary functions
> >> *
> >>
> >> @@ -5,16 +6,6 @@
> >>
> >> * Copyright (C) 2016 Shuah Khan <shuahkh@osg.samsung.com>
> >> * Copyright (C) 2006-2010 Nokia Corporation
> >> * Copyright (c) 2016 Intel Corporation.
> >>
> >> - *
> >> - * 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.
>
> Are you concerned about the "or (at your option) any later version." part
> that it doesn't match?
Yes, that's my concern. I'm personally fine with GPL-2.0-only, but you'll have
a hard time contacting all the other copyright holders if you want to
relicense this. Good luck getting hold of the appropriate legal department at
Nokia :-)
On a related note, I nowadays encourage developers to keep their copyright on
code they wrote when possible, and to at least negotiate that with their
employers.
> >> - *
> >> - * 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.
> >> */
> >>
> >> #include <linux/module.h>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-01-11 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180110163540.8396-1-shuahkh@osg.samsung.com>
2018-01-10 16:35 ` [PATCH] media: v4l2-core: v4l2-mc: Add SPDX license identifier Shuah Khan
2018-01-11 12:55 ` Laurent Pinchart
2018-01-11 15:45 ` Shuah Khan
2018-01-11 18:42 ` Laurent Pinchart [this message]
2018-01-11 20:44 ` Shuah Khan
2018-01-11 21:33 ` Laurent Pinchart
2018-01-11 22:10 ` Shuah Khan
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=1730571.xFN9zJKHcq@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.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