mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: [ptxdist] [PATCH v2] mmc-utils: add license files
Date: Tue, 18 Oct 2022 19:21:18 +0200	[thread overview]
Message-ID: <20221018172118.4196-1-bruno.thomsen@gmail.com> (raw)

Newly added README file clearly states that license is GPL-2.0-only.
3rdparty hmac_sha2 has a dual BSD and GPLv2 license when distributed
with mmc-utils.
Add README, mmc.c and 3rdparty/hmac_sha/sha2.h license header as license
files.

Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
 rules/mmc-utils.make | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/rules/mmc-utils.make b/rules/mmc-utils.make
index a5045b079..9a43c148b 100644
--- a/rules/mmc-utils.make
+++ b/rules/mmc-utils.make
@@ -23,6 +23,10 @@ MMC_UTILS_URL		:= https://git.kernel.org/pub/scm/utils/mmc/mmc-utils.git;tag=$(M
 MMC_UTILS_SOURCE	:= $(SRCDIR)/$(MMC_UTILS).$(MMC_UTILS_SUFFIX)
 MMC_UTILS_DIR		:= $(BUILDDIR)/$(MMC_UTILS)
 MMC_UTILS_LICENSE	:= GPL-2.0-only AND BSD-3-Clause
+MMC_UTILS_LICENSE_FILES := \
+	file://README;startline=28;endline=31;md5=73e5e3ce638b21eca6e204e260201d4a \
+	file://mmc.c;startline=1;endline=20;md5=fae32792e20f4d27ade1c5a762d16b7d \
+	file://3rdparty/hmac_sha/sha2.h;startline=1;endline=36;md5=6ce341e87c5fcac36e417f4a0e283afd
 
 # ----------------------------------------------------------------------------
 # Prepare

base-commit: 8b46f8923ebfeb2bd1ead374035255df1df26f85
-- 
2.37.3




             reply	other threads:[~2022-10-18 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 17:21 Bruno Thomsen [this message]
2022-10-28 14:44 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20221018172118.4196-1-bruno.thomsen@gmail.com \
    --to=bruno.thomsen@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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