Lines Matching refs:exception

8 with an explicit syscall exception described in
36 kernel, the exception must be documented by a special license expression.
96    exception applies. When multiple licenses apply, an expression consists
114       // SPDX-License-Identifier: GPL-2.0 WITH mif-exception
115       // SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0
118    valid License identifiers are listed in the tags of the exception text
291    exception text and the required `Exception Metatags`_.
297    Contains the Linux syscall exception as documented in the COPYING
301       LICENSES/exceptions/GCC-exception-2.0
303    Contains the GCC 'linking exception' which allows to link any binary
305    with this exception. This is required for creating runnable executables
310    The following meta tags must be available in an exception file:
314      One exception identifier which can be used with SPDX license
320      to the exception.
325      exception can be used.
335      All text after this tag is treated as the original exception text
343         This exception is used together with one of the above SPDX-Licenses
346         To use this exception add it with the keyword WITH to one of the
350         Full exception text
354       SPDX-Exception-Identifier: GCC-exception-2.0
355       SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
358         The "GCC Runtime Library exception 2.0" is used together with one
361         To use this exception add it with the keyword WITH to one of the
363 	  SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
365         Full exception text