From: Denys Dmytriyenko <denis@denix.org>
To: Jon Mason <jon.mason@arm.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH] arm/trusted-firmware-a: update LICENSE entry
Date: Fri, 30 Aug 2024 15:53:57 -0400 [thread overview]
Message-ID: <20240830195357.GF17572@denix.org> (raw)
In-Reply-To: <20240830155148.24392-1-jon.mason@arm.com>
On Fri, Aug 30, 2024 at 11:51:48AM -0400, Jon Mason wrote:
> As pointed out by Denys Dmytriyenko, the LICENSE entry in
> trusted-firmware-a is not accurate. docs/license.rst specifies the
> licenses to be BSD 3 Clause for the project, with code from other
> projects imported as:
> libc BSD-3-Clause
> libfdt BSD-2-Clause
> LLVM BSD-3-Clause
> zlib BSD-3-Clause
> STMicroelectronics platform source code BSD-3-Clause
> Linux source MIT
> DICE Apache 2.0
>
> Note: these are the license the code is imported with (according to
> license.rst), not a listing of the license(s) of those sources.
>
> Signed-off-by: Jon Mason <jon.mason@arm.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> index 80d41f328afa..f90b588444a4 100644
> --- a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> +++ b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> @@ -1,5 +1,5 @@
> DESCRIPTION = "Trusted Firmware-A"
> -LICENSE = "BSD-3-Clause & MIT"
> +LICENSE = "BSD-2-Clause & BSD-3-Clause & MIT & Apache-2.0"
>
> PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> --
> 2.39.3 (Apple Git-146)
next prev parent reply other threads:[~2024-08-30 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 15:51 [PATCH] arm/trusted-firmware-a: update LICENSE entry Jon Mason
2024-08-30 19:53 ` Denys Dmytriyenko [this message]
2024-09-03 15:32 ` Jon Mason
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=20240830195357.GF17572@denix.org \
--to=denis@denix.org \
--cc=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.