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.bar...@sancloud.com>
Cc: Wolfgang Denk <w...@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
 
-- 
2.25.1

Reply via email to