Lines Matching full:exception

10 with an explicit syscall exception described in
38 kernel, the exception must be documented by a special license expression.
101    exception applies. When multiple licenses apply, an expression consists
119       // SPDX-License-Identifier: GPL-2.0 WITH mif-exception
120       // SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0
123    valid License identifiers are listed in the tags of the exception text
345    exception text and the required `Exception Metatags`_.
351    Contains the Linux syscall exception as documented in the COPYING
355       LICENSES/exceptions/GCC-exception-2.0
357    Contains the GCC 'linking exception' which allows to link any binary
359    with this exception. This is required for creating runnable executables
362    _`Exception Metatags`:
364    The following meta tags must be available in an exception file:
366    - SPDX-Exception-Identifier:
368      One exception identifier which can be used with SPDX license
374      to the exception.
379      exception can be used.
387    - Exception-Text:
389      All text after this tag is treated as the original exception text
393       SPDX-Exception-Identifier: Linux-syscall-note
397         This exception is used together with one of the above SPDX-Licenses
400         To use this exception add it with the keyword WITH to one of the
403       Exception-Text:
404         Full exception text
408       SPDX-Exception-Identifier: GCC-exception-2.0
409       SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
412         The "GCC Runtime Library exception 2.0" is used together with one
415         To use this exception add it with the keyword WITH to one of the
417 	  SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
418       Exception-Text:
419         Full exception text