From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Mikhail Zaslonko <zaslonko@linux.ibm.com>
Cc: linux-spdx@vger.kernel.org
Subject: ./scripts/spdxcheck.py warns Invalid License ID: Zlib
Date: Sun, 22 Mar 2020 18:29:06 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2003221825220.10666@felia> (raw)
Dear Ilya, dear Mikhail,
thank you for pointing out clear original authorship and license
information in the files you have contributed.
Due to these pointers, ./scripts/spdxcheck.py has identified these files
licensed under the Zlib License and reports:
lib/zlib_dfltcc/dfltcc.c: 1:28 Invalid License ID: Zlib
lib/zlib_dfltcc/dfltcc.h: 1:28 Invalid License ID: Zlib
lib/zlib_dfltcc/dfltcc_deflate.c: 1:28 Invalid License ID: Zlib
lib/zlib_dfltcc/dfltcc_inflate.c: 1:28 Invalid License ID: Zlib
lib/zlib_dfltcc/dfltcc_util.h: 1:28 Invalid License ID: Zlib
As there is currently no Zlib license text in LICENSES, I believe you must
simply add the Zlib license text to LICENSES/deprecated. The documentation
states deprecated licenses should only be used for existing code or for
importing code from a different project, which is the case here.
Just in case you are not aware, more documentation on licensing is here:
https://www.kernel.org/doc/html/latest/process/license-rules.html
Best regards,
Lukas
reply other threads:[~2020-03-22 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.21.2003221825220.10666@felia \
--to=lukas.bulwahn@gmail.com \
--cc=iii@linux.ibm.com \
--cc=linux-spdx@vger.kernel.org \
--cc=zaslonko@linux.ibm.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).