From: Peter Korsgaard <peter@korsgaard.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openocd: add the eCos exception to the GPL-2.0+ license
Date: Sun, 23 Apr 2023 12:42:57 +0200 [thread overview]
Message-ID: <874jp66fri.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230422133607.607954-1-dario.binacchi@amarulasolutions.com> (Dario Binacchi's message of "Sat, 22 Apr 2023 15:36:07 +0200")
>>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:
> As noted by Yann E. MORIN in [1] only the src/flash/nand/ecc.c file
> refers to the eCos license.
> The SPDX identifier for that file is:
> SPDX-License-Identifier: GPL-2.0-or-later WITH eCos-exception-2.0
> The file is part of the openocd executable via libopenocd.la, which being
> a static library it is not installed.
> Based on this, becomes more natural to associate the eCos exception with
> the GPL 2.0+ license, rather than considering it separately as a license.
> [1] https://patchwork.ozlabs.org/project/buildroot/patch/20230411203930.2455301-1-dario.binacchi@amarulasolutions.com/
> Suggested-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-04-23 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 13:36 [Buildroot] [PATCH 1/1] package/openocd: add the eCos exception to the GPL-2.0+ license Dario Binacchi
2023-04-23 9:41 ` Yann E. MORIN
2023-04-23 10:42 ` Peter Korsgaard [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=874jp66fri.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=yann.morin.1998@free.fr \
/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