Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: 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 11:41:59 +0200	[thread overview]
Message-ID: <20230423094159.GB2696@scaer> (raw)
In-Reply-To: <20230422133607.607954-1-dario.binacchi@amarulasolutions.com>

Dario, All,

On 2023-04-22 15:36 +0200, Dario Binacchi spake thusly:
> 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>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/openocd/openocd.mk | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/package/openocd/openocd.mk b/package/openocd/openocd.mk
> index 9973498cf568..78c6e10c58e4 100644
> --- a/package/openocd/openocd.mk
> +++ b/package/openocd/openocd.mk
> @@ -8,14 +8,13 @@ OPENOCD_VERSION = 0.12.0
>  OPENOCD_SOURCE = openocd-$(OPENOCD_VERSION).tar.bz2
>  OPENOCD_SITE = http://sourceforge.net/projects/openocd/files/openocd/$(OPENOCD_VERSION)
>  OPENOCD_LICENSE = \
> -	eCos-exception-2.0, \
>  	BSD-1-clause, \
>  	BSD-2-clause, \
>  	BSD-2-Clause-Views, \
>  	BSD-3-clause, \
>  	BSD-Source-Code, \
>  	GFDL-1.2-no-invariants-or-later (docs), \
> -	GPL-2.0+ (code), \
> +	GPL-2.0+ with eCos-exception-2.0 (code), \
>  	GPL-3.0+ (stand-alone code), \
>  	MIT
>  
> -- 
> 2.32.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-04-23  9:42 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 [this message]
2023-04-23 10:42 ` Peter Korsgaard

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=20230423094159.GB2696@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    /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