From: Diederik de Haas <didi.debian@cknow.org>
To: linux-firmware@kernel.org
Subject: License and copyright on 'native' files?
Date: Wed, 07 Feb 2024 15:48:20 +0100 [thread overview]
Message-ID: <2958104.rSODG2ex0Y@bagend> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Hi,
Lintian reported several file-without-copyright-information wrt the repo's
'native' files, like Makefile, README, WHENCE and that'll likely also apply to
Dockerfile and the various dotfiles.
The Gitlab repo indicates it's Apache 2.0, but I'm not sure whether that is
correct or that gitlab assumed it was due to some heuristics.
The README.md does mention "in a GPL'd work", but I'm guessing that refers to
the GPL-2.0 of the kernel itself.
I saw that 'copy-firmware.sh' is licensed under GPL-2.0, but the other files I
checked didn't indicate the license of those files. And none (?) seem to have a
copyright statement.
Can the license and copyright (situation) be clarified?
Regards,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2024-02-07 14:48 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=2958104.rSODG2ex0Y@bagend \
--to=didi.debian@cknow.org \
--cc=linux-firmware@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).