From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: Re: [ptxdist] [APPLIED] host-dtc: add missing license
Date: Fri, 11 Mar 2022 10:25:04 +0100 [thread overview]
Message-ID: <20220311092504.2010152-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220218155441.899919-1-michael.riesch@wolfvision.net>
Thanks, applied as a24ee7a9f58c78d5f836c958fcc71cf3892420fb.
Michael
[sent from post-receive hook]
On Fri, 11 Mar 2022 10:25:03 +0100, Michael Riesch <michael.riesch@wolfvision.net> wrote:
> The README.license states that the libfdt is dual-licensed (BSD-2-Clause
> OR GPL-2.0-only), but the dtc itself is licensed as GPL-2.0-only.
>
> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> Message-Id: <20220218155441.899919-1-michael.riesch@wolfvision.net>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/host-dtc.make b/rules/host-dtc.make
> index 958eada01eb1..19551203e9ba 100644
> --- a/rules/host-dtc.make
> +++ b/rules/host-dtc.make
> @@ -22,6 +22,7 @@ HOST_DTC_SUFFIX := tar.gz
> HOST_DTC_URL := https://git.kernel.org/pub/scm/utils/dtc/dtc.git/snapshot/$(HOST_DTC).$(HOST_DTC_SUFFIX)
> HOST_DTC_SOURCE := $(SRCDIR)/$(HOST_DTC).$(HOST_DTC_SUFFIX)
> HOST_DTC_DIR := $(HOST_BUILDDIR)/$(HOST_DTC)
> +HOST_DTC_LICENSE := GPL-2.0-only
>
> # ----------------------------------------------------------------------------
> # Prepare
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2022-03-11 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 15:54 [ptxdist] [PATCH] " Michael Riesch
2022-03-11 9:25 ` 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=20220311092504.2010152-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
--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