Lines Matching refs:exception
10 with an explicit syscall exception described in
38 kernel, the exception must be documented by a special license expression.
98 exception applies. When multiple licenses apply, an expression consists
116 // SPDX-License-Identifier: GPL-2.0 WITH mif-exception
117 // SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0
120 valid License identifiers are listed in the tags of the exception text
342 exception text and the required `Exception Metatags`_.
348 Contains the Linux syscall exception as documented in the COPYING
352 LICENSES/exceptions/GCC-exception-2.0
354 Contains the GCC 'linking exception' which allows to link any binary
356 with this exception. This is required for creating runnable executables
361 The following meta tags must be available in an exception file:
365 One exception identifier which can be used with SPDX license
371 to the exception.
376 exception can be used.
386 All text after this tag is treated as the original exception text
394 This exception is used together with one of the above SPDX-Licenses
397 To use this exception add it with the keyword WITH to one of the
401 Full exception text
405 SPDX-Exception-Identifier: GCC-exception-2.0
406 SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
409 The "GCC Runtime Library exception 2.0" is used together with one
412 To use this exception add it with the keyword WITH to one of the
414 SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
416 Full exception text