From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: Re: License clarification of sound/soc/qcom/qdsp6/q6afe-clocks.c
Date: Sat, 26 Sep 2020 18:19:07 +0100 [thread overview]
Message-ID: <dab67d9c-8ef6-bf41-dd9a-fbd6e29d6818@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2009261855280.31589@felia>
Thanks Lukas for spotting this,
On 26/09/2020 18:01, Lukas Bulwahn wrote:
> At the end of the file, you further state it licensed with GPL-2.0 with
> the following line:
>
> MODULE_LICENSE("GPL v2");
>
> So, is this just a typo in the SPDX-License-Identifier or do you really
> intend to license this file under GPL-1.0 only?
yes, this was totally unintended typo from my side, Just sent a patch to
fix this!
thanks,
srini
prev parent reply other threads:[~2020-09-26 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 17:01 License clarification of sound/soc/qcom/qdsp6/q6afe-clocks.c Lukas Bulwahn
2020-09-26 17:19 ` Srinivas Kandagatla [this message]
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=dab67d9c-8ef6-bf41-dd9a-fbd6e29d6818@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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;
as well as URLs for NNTP newsgroup(s).