From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, vinod.koul@linaro.org,
tiwai@suse.de, mengdong.lin@intel.com,
ranjani.sridharan@linux.intel.com, linux-kernel@vger.kernel.org,
hui.wang@canonical.com, vkoul@kernel.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
slawomir.blauciak@intel.com, sanyog.r.kale@intel.com,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH] soundwire: clarify SPDX use of GPL-2.0
Date: Mon, 1 Jun 2020 15:50:13 -0500 [thread overview]
Message-ID: <686345af-4fda-4bc1-c3bf-da31406e806b@linux.intel.com> (raw)
In-Reply-To: <20200601053809.GA1420218@kroah.com>
On 6/1/20 12:38 AM, Greg KH wrote:
> On Mon, Jun 01, 2020 at 01:28:07AM +0800, Bard Liao wrote:
>> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>>
>> Change SPDX from GPL-2.0 to GPL-2.0-only for Intel-contributed
>> code. This was explicit before the transition to SPDX and lost in
>> translation.
>
> It is also explicit in the "GPL-2.0" lines as well, did you read the
> LICENSES/preferred/GPL-2.0 file for the allowed tags to be used for this
> license?
>
> So this doesn't change anything, and we are trying to cut down on this
> type of churn until, maybe, after the whole kernel has proper SPDX
> lines.
My commit message was misleading, sorry. For SoundWire, we recently
added new files with GPL-2.0-only (master + sysfs), as recommended since
the short GPL-2.0 identifier is deprecated
(https://spdx.org/licenses/GPL-2.0.html https://spdx.org/licenses/).
Intel does not mind if we delay this change, you are right that this
doesn't change anything license-wise. I just felt it was a good time to
align old and new contributions to avoid having half of the files with
GPL-2.0 and half with GPL-2.0-only.
We still have quite a few patches for SoundWire (~80 coming w/ 7k lines
changed), so those changes are really minimal in comparison with the
actual 'churn' to fix programming sequences, power management,
multi-link management and bit allocation.
Oh and this was not intended to be added to 5.8 btw or pulled as a fix,
really nothing to do with the merge window.
If you prefer us to keep this change on the back burner, that's fine,
the only intent was to keep all SoundWire-related files consistent.
next prev parent reply other threads:[~2020-06-01 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 17:28 [PATCH] soundwire: clarify SPDX use of GPL-2.0 Bard Liao
2020-06-01 5:38 ` Greg KH
2020-06-01 20:50 ` Pierre-Louis Bossart [this message]
2020-06-02 9:02 ` Greg KH
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=686345af-4fda-4bc1-c3bf-da31406e806b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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