From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] mmc-utils: add license files
Date: Fri, 28 Oct 2022 16:44:16 +0200 [thread overview]
Message-ID: <20221028144416.2255849-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221018172118.4196-1-bruno.thomsen@gmail.com>
Thanks, applied as c6a4247915452a018cce9e55e2ab929dcab30ead.
Michael
[sent from post-receive hook]
On Fri, 28 Oct 2022 16:44:16 +0200, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> 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>
> Message-Id: <20221018172118.4196-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/mmc-utils.make b/rules/mmc-utils.make
> index a5045b079c1e..9a43c148b112 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
prev parent reply other threads:[~2022-10-28 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 17:21 [ptxdist] [PATCH v2] " Bruno Thomsen
2022-10-28 14:44 ` Michael Olbrich [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=20221028144416.2255849-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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