From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier
Date: Thu, 14 Dec 2017 21:05:27 +0200 [thread overview]
Message-ID: <2967655.MWOA0IsQOS@avalon> (raw)
In-Reply-To: <1513277679.27409.83.camel@perches.com>
Hi Joe,
(CC'ing Greg and adding context for easier understanding)
On Thursday, 14 December 2017 20:54:39 EET Joe Perches wrote:
> On Thu, 2017-12-14 at 20:37 +0200, Laurent Pinchart wrote:
> > On Thursday, 14 December 2017 20:32:20 EET Joe Perches wrote:
> >> On Thu, 2017-12-14 at 20:28 +0200, Laurent Pinchart wrote:
> >>> On Thursday, 14 December 2017 19:05:27 EET Mauro Carvalho Chehab wrote:
> >>>> Em Fri, 8 Dec 2017 18:05:37 +0530 Dhaval Shah escreveu:
> >>>>> SPDX-License-Identifier is used for the Xilinx Video IP and
> >>>>> related drivers.
> >>>>>
> >>>>> Signed-off-by: Dhaval Shah <dhaval23031987@gmail.com>
> >>>>
> >>>> Hi Dhaval,
> >>>>
> >>>> You're not listed as one of the Xilinx driver maintainers. I'm afraid
> >>>> that, without their explicit acks, sent to the ML, I can't accept a
> >>>> patch touching at the driver's license tags.
> >>>
> >>> The patch doesn't change the license, I don't see why it would cause
> >>> any issue. Greg isn't listed as the maintainer or copyright holder of
> >>> any of the 10k+ files to which he added an SPDX license header in the
> >>> last kernel release.\0\0\0
> >>
> >> Adding a comment line that describes an implicit or
> >> explicit license is different than removing the license
> >> text itself.
> >
> > The SPDX license header is meant to be equivalent to the license text.
>
> I understand that.
> At a minimum, removing BSD license text is undesirable
> as that license states:
>
> * * Redistributions of source code must retain the above copyright
> * notice, this list of conditions and the following disclaimer.
> etc...
But this patch only removes the following text:
- * This program is free software; you can redistribute it and/or modify
- * it under the terms of the GNU General Public License version 2 as
- * published by the Free Software Foundation.
and replaces it by the corresponding SPDX header.
> > The only reason why the large SPDX patch didn't touch the whole kernel in
> > one go was that it was easier to split in in multiple chunks.
>
> Not really, it was scripted.
But still manually reviewed as far as I know.
> > This is no different than not including the full GPL license in every
> > header file but only pointing to it through its name and reference, as
> > every kernel source file does.
>
> Not every kernel source file had a license text
> or a reference to another license file.
Correct, but the files touched by this patch do.
This issue is in no way specific to linux-media and should be decided upon at
the top level, not on a per-subsystem basis. Greg, could you comment on this ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-12-14 19:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 12:35 [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier Dhaval Shah
2017-12-11 13:47 ` Laurent Pinchart
2017-12-12 6:09 ` Dhaval Shah
2017-12-14 17:05 ` Mauro Carvalho Chehab
2017-12-14 17:26 ` Joe Perches
2017-12-14 17:35 ` Mauro Carvalho Chehab
2017-12-14 18:28 ` Laurent Pinchart
2017-12-14 18:32 ` Joe Perches
2017-12-14 18:37 ` Laurent Pinchart
2017-12-14 18:54 ` Joe Perches
2017-12-14 19:05 ` Laurent Pinchart [this message]
2017-12-14 20:08 ` Greg KH
2017-12-14 20:44 ` Laurent Pinchart
2017-12-14 20:57 ` Greg KH
2017-12-14 21:50 ` Mauro Carvalho Chehab
2017-12-14 22:02 ` Laurent Pinchart
2017-12-15 5:25 ` Dhaval Shah
2017-12-15 9:27 ` Mauro Carvalho Chehab
2017-12-18 7:32 ` Michal Simek
2017-12-18 8:32 ` Laurent Pinchart
2017-12-18 8:56 ` Michal Simek
2018-01-08 12:30 ` Michal Simek
2017-12-15 9:23 ` Mauro Carvalho Chehab
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=2967655.MWOA0IsQOS@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).