From: Joe Perches <joe@perches.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Dhaval Shah <dhaval23031987@gmail.com>,
hyun.kwon@xilinx.com, michal.simek@xilinx.com,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier
Date: Thu, 14 Dec 2017 10:54:39 -0800 [thread overview]
Message-ID: <1513277679.27409.83.camel@perches.com> (raw)
In-Reply-To: <16301043.Lbu0ahMgBI@avalon>
On Thu, 2017-12-14 at 20:37 +0200, Laurent Pinchart wrote:
> Hi Joe,
Hi Laurent.
> On Thursday, 14 December 2017 20:32:20 EET Joe Perches wrote:
> > 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...
> 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.
> 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.
next prev parent reply other threads:[~2017-12-14 18:54 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 [this message]
2017-12-14 19:05 ` Laurent Pinchart
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=1513277679.27409.83.camel@perches.com \
--to=joe@perches.com \
--cc=dhaval23031987@gmail.com \
--cc=hyun.kwon@xilinx.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michal.simek@xilinx.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