From: Tom Rini <trini@konsulko.com>
To: Paul Barker <paul.barker@sancloud.com>, Wolfgang Denk <wd@denx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] Licenses: Clarify exceptions for standalone apps
Date: Wed, 11 May 2022 09:34:13 -0400 [thread overview]
Message-ID: <20220511133413.GO3901321@bill-the-cat> (raw)
In-Reply-To: <20220505153242.1598807-2-paul.barker@sancloud.com>
[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]
On Thu, May 05, 2022 at 03:32:40PM +0000, Paul Barker wrote:
> On 2010-01-27, an email [1] was sent to the mailing list by Wolfgang
> Denk which clarified the intended licensing exceptions for standalone
> applications. As the "export.h" header and the "stubs.c" source files
> are required to implement a standalone application, the intention was
> that these files be covered by the licensing exception. This is made
> clear in the following quotes from that email:
>
> "exports.h" should be added to the "allowed" file list; there should
> be no need to include "common.h". Eventually this needs fixing.
> Patches are welcome.
>
> "examples/standalone/stubs.c" should be added to the "allowed" file
> list (the ppc_*jmp.S files are LGPLed).
>
> There should be no doubts - the intention is clear, the current state
> may need improvement. Help (read: patches) welcome.
>
> [1]: https://lists.denx.de/pipermail/u-boot/2010-January/067174.html
>
> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
> Cc: Wolfgang Denk <wd@denx.de>
> ---
> Licenses/Exceptions | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/Licenses/Exceptions b/Licenses/Exceptions
> index c9b3cd981f51..4f241f4aff29 100644
> --- a/Licenses/Exceptions
> +++ b/Licenses/Exceptions
> @@ -7,9 +7,13 @@ use U-Boot services by means of the jump table provided by U-Boot
> exactly for this purpose - this is merely considered normal use of
> U-Boot, and does *not* fall under the heading of "derived work".
>
> - The header files "include/image.h" and "arch/*/include/asm/u-boot.h"
> -define interfaces to U-Boot. Including these (unmodified) header
> -files in another file is considered normal use of U-Boot, and does
> -*not* fall under the heading of "derived work".
> +The following files define interfaces to U-Boot:
> + * include/image.h
> + * include/export.h
> + * arch/*/include/asm/u-boot.h
> + * examples/standalone/stubs.c
> +
> +Including these (unmodified) files in another file is considered normal
> +use of U-Boot, and does *not* fall under the heading of "derived work".
> -- Wolfgang Denk
Wolfgang?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-05-11 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:32 [PATCH 0/3] Clarify standalone application support Paul Barker
2022-05-05 15:32 ` [PATCH 1/3] Licenses: Clarify exceptions for standalone apps Paul Barker
2022-05-11 13:34 ` Tom Rini [this message]
2022-08-26 13:35 ` Wolfgang Denk
2022-10-26 19:26 ` Tom Rini
2022-05-05 15:32 ` [PATCH 2/3] examples: hello_world: Drop inclusion of common header Paul Barker
2022-05-11 13:34 ` Tom Rini
2022-08-26 13:36 ` Wolfgang Denk
2022-10-26 19:26 ` Tom Rini
2022-05-05 15:32 ` [PATCH 3/3] exports: Fix export of SPI access functions Paul Barker
2022-05-11 13:34 ` Tom Rini
2022-08-26 13:42 ` Wolfgang Denk
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=20220511133413.GO3901321@bill-the-cat \
--to=trini@konsulko.com \
--cc=paul.barker@sancloud.com \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.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