1 .. SPDX-License-Identifier: GPL-2.0 1 .. SPDX-License-Identifier: GPL-2.0
2 2
3 .. _kernel_licensing: <<
4 <<
5 Linux kernel licensing rules 3 Linux kernel licensing rules
6 ============================ 4 ============================
7 5
8 The Linux Kernel is provided under the terms o 6 The Linux Kernel is provided under the terms of the GNU General Public
9 License version 2 only (GPL-2.0), as provided !! 7 License version 2 only (GPL-2.0), as published by the Free Software
10 with an explicit syscall exception described i !! 8 Foundation, and provided in the COPYING file. This documentation file is
11 LICENSES/exceptions/Linux-syscall-note, as des !! 9 not meant to replace the COPYING file, but provides a description of how
12 !! 10 each source file should be annotated to make the licensing it is governed
13 This documentation file provides a description !! 11 under clear and unambiguous.
14 should be annotated to make its license clear !! 12
15 It doesn't replace the Kernel's license. !! 13 The license in the COPYING file applies to the kernel source as a whole,
16 !! 14 though individual source files can have a different license which is
17 The license described in the COPYING file appl !! 15 required to be compatible with the GPL-2.0::
18 as a whole, though individual source files can <<
19 which is required to be compatible with the GP <<
20 16
21 GPL-1.0+ : GNU General Public License v1 17 GPL-1.0+ : GNU General Public License v1.0 or later
22 GPL-2.0+ : GNU General Public License v2 18 GPL-2.0+ : GNU General Public License v2.0 or later
23 LGPL-2.0 : GNU Library General Public Li 19 LGPL-2.0 : GNU Library General Public License v2 only
24 LGPL-2.0+ : GNU Library General Public Li 20 LGPL-2.0+ : GNU Library General Public License v2 or later
25 LGPL-2.1 : GNU Lesser General Public Lic 21 LGPL-2.1 : GNU Lesser General Public License v2.1 only
26 LGPL-2.1+ : GNU Lesser General Public Lic 22 LGPL-2.1+ : GNU Lesser General Public License v2.1 or later
27 23
28 Aside from that, individual files can be provi 24 Aside from that, individual files can be provided under a dual license,
29 e.g. one of the compatible GPL variants and al 25 e.g. one of the compatible GPL variants and alternatively under a
30 permissive license like BSD, MIT etc. 26 permissive license like BSD, MIT etc.
31 27
32 The User-space API (UAPI) header files, which 28 The User-space API (UAPI) header files, which describe the interface of
33 user-space programs to the kernel are a specia 29 user-space programs to the kernel are a special case. According to the
34 note in the kernel COPYING file, the syscall i 30 note in the kernel COPYING file, the syscall interface is a clear boundary,
35 which does not extend the GPL requirements to 31 which does not extend the GPL requirements to any software which uses it to
36 communicate with the kernel. Because the UAPI 32 communicate with the kernel. Because the UAPI headers must be includable
37 into any source files which create an executab 33 into any source files which create an executable running on the Linux
38 kernel, the exception must be documented by a 34 kernel, the exception must be documented by a special license expression.
39 35
40 The common way of expressing the license of a 36 The common way of expressing the license of a source file is to add the
41 matching boilerplate text into the top comment 37 matching boilerplate text into the top comment of the file. Due to
42 formatting, typos etc. these "boilerplates" ar 38 formatting, typos etc. these "boilerplates" are hard to validate for
43 tools which are used in the context of license 39 tools which are used in the context of license compliance.
44 40
45 An alternative to boilerplate text is the use 41 An alternative to boilerplate text is the use of Software Package Data
46 Exchange (SPDX) license identifiers in each so 42 Exchange (SPDX) license identifiers in each source file. SPDX license
47 identifiers are machine parsable and precise s 43 identifiers are machine parsable and precise shorthands for the license
48 under which the content of the file is contrib 44 under which the content of the file is contributed. SPDX license
49 identifiers are managed by the SPDX Workgroup 45 identifiers are managed by the SPDX Workgroup at the Linux Foundation and
50 have been agreed on by partners throughout the 46 have been agreed on by partners throughout the industry, tool vendors, and
51 legal teams. For further information see http 47 legal teams. For further information see https://spdx.org/
52 48
53 The Linux kernel requires the precise SPDX ide 49 The Linux kernel requires the precise SPDX identifier in all source files.
54 The valid identifiers used in the kernel are e 50 The valid identifiers used in the kernel are explained in the section
55 `License identifiers`_ and have been retrieved 51 `License identifiers`_ and have been retrieved from the official SPDX
56 license list at https://spdx.org/licenses/ alo 52 license list at https://spdx.org/licenses/ along with the license texts.
57 53
58 License identifier syntax 54 License identifier syntax
59 ------------------------- 55 -------------------------
60 56
61 1. Placement: 57 1. Placement:
62 58
63 The SPDX license identifier in kernel files 59 The SPDX license identifier in kernel files shall be added at the first
64 possible line in a file which can contain a 60 possible line in a file which can contain a comment. For the majority
65 of files this is the first line, except for !! 61 or files this is the first line, except for scripts which require the
66 '#!PATH_TO_INTERPRETER' in the first line. 62 '#!PATH_TO_INTERPRETER' in the first line. For those scripts the SPDX
67 identifier goes into the second line. 63 identifier goes into the second line.
68 64
69 | 65 |
70 66
71 2. Style: 67 2. Style:
72 68
73 The SPDX license identifier is added in for 69 The SPDX license identifier is added in form of a comment. The comment
74 style depends on the file type:: 70 style depends on the file type::
75 71
76 C source: // SPDX-License-Identifier: <S 72 C source: // SPDX-License-Identifier: <SPDX License Expression>
77 C header: /* SPDX-License-Identifier: <S 73 C header: /* SPDX-License-Identifier: <SPDX License Expression> */
78 ASM: /* SPDX-License-Identifier: <S 74 ASM: /* SPDX-License-Identifier: <SPDX License Expression> */
79 scripts: # SPDX-License-Identifier: <SP 75 scripts: # SPDX-License-Identifier: <SPDX License Expression>
80 .rst: .. SPDX-License-Identifier: <S 76 .rst: .. SPDX-License-Identifier: <SPDX License Expression>
81 .dts{i}: // SPDX-License-Identifier: <S 77 .dts{i}: // SPDX-License-Identifier: <SPDX License Expression>
82 78
83 If a specific tool cannot handle the standa 79 If a specific tool cannot handle the standard comment style, then the
84 appropriate comment mechanism which the too 80 appropriate comment mechanism which the tool accepts shall be used. This
85 is the reason for having the "/\* \*/" styl 81 is the reason for having the "/\* \*/" style comment in C header
86 files. There was build breakage observed wi 82 files. There was build breakage observed with generated .lds files where
87 'ld' failed to parse the C++ comment. This 83 'ld' failed to parse the C++ comment. This has been fixed by now, but
88 there are still older assembler tools which 84 there are still older assembler tools which cannot handle C++ style
89 comments. 85 comments.
90 86
91 | 87 |
92 88
93 3. Syntax: 89 3. Syntax:
94 90
95 A <SPDX License Expression> is either an SP 91 A <SPDX License Expression> is either an SPDX short form license
96 identifier found on the SPDX License List, 92 identifier found on the SPDX License List, or the combination of two
97 SPDX short form license identifiers separat 93 SPDX short form license identifiers separated by "WITH" when a license
98 exception applies. When multiple licenses a 94 exception applies. When multiple licenses apply, an expression consists
99 of keywords "AND", "OR" separating sub-expr 95 of keywords "AND", "OR" separating sub-expressions and surrounded by
100 "(", ")" . 96 "(", ")" .
101 97
102 License identifiers for licenses like [L]GP 98 License identifiers for licenses like [L]GPL with the 'or later' option
103 are constructed by using a "+" for indicati 99 are constructed by using a "+" for indicating the 'or later' option.::
104 100
105 // SPDX-License-Identifier: GPL-2.0+ 101 // SPDX-License-Identifier: GPL-2.0+
106 // SPDX-License-Identifier: LGPL-2.1+ 102 // SPDX-License-Identifier: LGPL-2.1+
107 103
108 WITH should be used when there is a modifie 104 WITH should be used when there is a modifier to a license needed.
109 For example, the linux kernel UAPI files us 105 For example, the linux kernel UAPI files use the expression::
110 106
111 // SPDX-License-Identifier: GPL-2.0 WITH 107 // SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
112 // SPDX-License-Identifier: GPL-2.0+ WIT 108 // SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note
113 109
114 Other examples using WITH exceptions found 110 Other examples using WITH exceptions found in the kernel are::
115 111
116 // SPDX-License-Identifier: GPL-2.0 WITH 112 // SPDX-License-Identifier: GPL-2.0 WITH mif-exception
117 // SPDX-License-Identifier: GPL-2.0+ WIT 113 // SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0
118 114
119 Exceptions can only be used with particular 115 Exceptions can only be used with particular License identifiers. The
120 valid License identifiers are listed in the 116 valid License identifiers are listed in the tags of the exception text
121 file. For details see the point `Exceptions 117 file. For details see the point `Exceptions`_ in the chapter `License
122 identifiers`_. 118 identifiers`_.
123 119
124 OR should be used if the file is dual licen 120 OR should be used if the file is dual licensed and only one license is
125 to be selected. For example, some dtsi fil 121 to be selected. For example, some dtsi files are available under dual
126 licenses:: 122 licenses::
127 123
128 // SPDX-License-Identifier: GPL-2.0 OR B 124 // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
129 125
130 Examples from the kernel for license expres 126 Examples from the kernel for license expressions in dual licensed files::
131 127
132 // SPDX-License-Identifier: GPL-2.0 OR M 128 // SPDX-License-Identifier: GPL-2.0 OR MIT
133 // SPDX-License-Identifier: GPL-2.0 OR B 129 // SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
134 // SPDX-License-Identifier: GPL-2.0 OR A 130 // SPDX-License-Identifier: GPL-2.0 OR Apache-2.0
135 // SPDX-License-Identifier: GPL-2.0 OR M 131 // SPDX-License-Identifier: GPL-2.0 OR MPL-1.1
136 // SPDX-License-Identifier: (GPL-2.0 WIT 132 // SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) OR MIT
137 // SPDX-License-Identifier: GPL-1.0+ OR 133 // SPDX-License-Identifier: GPL-1.0+ OR BSD-3-Clause OR OpenSSL
138 134
139 AND should be used if the file has multiple 135 AND should be used if the file has multiple licenses whose terms all
140 apply to use the file. For example, if code 136 apply to use the file. For example, if code is inherited from another
141 project and permission has been given to pu 137 project and permission has been given to put it in the kernel, but the
142 original license terms need to remain in ef 138 original license terms need to remain in effect::
143 139
144 // SPDX-License-Identifier: (GPL-2.0 WIT 140 // SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) AND MIT
145 141
146 Another other example where both sets of li 142 Another other example where both sets of license terms need to be
147 adhered to is:: 143 adhered to is::
148 144
149 // SPDX-License-Identifier: GPL-1.0+ AND 145 // SPDX-License-Identifier: GPL-1.0+ AND LGPL-2.1+
150 146
151 License identifiers 147 License identifiers
152 ------------------- 148 -------------------
153 149
154 The licenses currently used, as well as the li 150 The licenses currently used, as well as the licenses for code added to the
155 kernel, can be broken down into: 151 kernel, can be broken down into:
156 152
157 1. _`Preferred licenses`: 153 1. _`Preferred licenses`:
158 154
159 Whenever possible these licenses should be 155 Whenever possible these licenses should be used as they are known to be
160 fully compatible and widely used. These li 156 fully compatible and widely used. These licenses are available from the
161 directory:: 157 directory::
162 158
163 LICENSES/preferred/ 159 LICENSES/preferred/
164 160
165 in the kernel source tree. 161 in the kernel source tree.
166 162
167 The files in this directory contain the ful 163 The files in this directory contain the full license text and
168 `Metatags`_. The file names are identical 164 `Metatags`_. The file names are identical to the SPDX license
169 identifier which shall be used for the lice 165 identifier which shall be used for the license in source files.
170 166
171 Examples:: 167 Examples::
172 168
173 LICENSES/preferred/GPL-2.0 169 LICENSES/preferred/GPL-2.0
174 170
175 Contains the GPL version 2 license text and 171 Contains the GPL version 2 license text and the required metatags::
176 172
177 LICENSES/preferred/MIT 173 LICENSES/preferred/MIT
178 174
179 Contains the MIT license text and the requi 175 Contains the MIT license text and the required metatags
180 176
181 _`Metatags`: 177 _`Metatags`:
182 178
183 The following meta tags must be available i 179 The following meta tags must be available in a license file:
184 180
185 - Valid-License-Identifier: 181 - Valid-License-Identifier:
186 182
187 One or more lines which declare which Lic 183 One or more lines which declare which License Identifiers are valid
188 inside the project to reference this part 184 inside the project to reference this particular license text. Usually
189 this is a single valid identifier, but e. 185 this is a single valid identifier, but e.g. for licenses with the 'or
190 later' options two identifiers are valid. 186 later' options two identifiers are valid.
191 187
192 - SPDX-URL: 188 - SPDX-URL:
193 189
194 The URL of the SPDX page which contains a 190 The URL of the SPDX page which contains additional information related
195 to the license. 191 to the license.
196 192
197 - Usage-Guidance: 193 - Usage-Guidance:
198 194
199 Freeform text for usage advice. The text 195 Freeform text for usage advice. The text must include correct examples
200 for the SPDX license identifiers as they 196 for the SPDX license identifiers as they should be put into source
201 files according to the `License identifie 197 files according to the `License identifier syntax`_ guidelines.
202 198
203 - License-Text: 199 - License-Text:
204 200
205 All text after this tag is treated as the 201 All text after this tag is treated as the original license text
206 202
207 File format examples:: 203 File format examples::
208 204
209 Valid-License-Identifier: GPL-2.0 205 Valid-License-Identifier: GPL-2.0
210 Valid-License-Identifier: GPL-2.0+ 206 Valid-License-Identifier: GPL-2.0+
211 SPDX-URL: https://spdx.org/licenses/GPL- 207 SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
212 Usage-Guide: 208 Usage-Guide:
213 To use this license in source code, pu 209 To use this license in source code, put one of the following SPDX
214 tag/value pairs into a comment accordi 210 tag/value pairs into a comment according to the placement
215 guidelines in the licensing rules docu 211 guidelines in the licensing rules documentation.
216 For 'GNU General Public License (GPL) 212 For 'GNU General Public License (GPL) version 2 only' use:
217 SPDX-License-Identifier: GPL-2.0 213 SPDX-License-Identifier: GPL-2.0
218 For 'GNU General Public License (GPL) 214 For 'GNU General Public License (GPL) version 2 or any later version' use:
219 SPDX-License-Identifier: GPL-2.0+ 215 SPDX-License-Identifier: GPL-2.0+
220 License-Text: 216 License-Text:
221 Full license text 217 Full license text
222 218
223 :: 219 ::
224 220
225 SPDX-License-Identifier: MIT 221 SPDX-License-Identifier: MIT
226 SPDX-URL: https://spdx.org/licenses/MIT. 222 SPDX-URL: https://spdx.org/licenses/MIT.html
227 Usage-Guide: 223 Usage-Guide:
228 To use this license in source code, pu 224 To use this license in source code, put the following SPDX
229 tag/value pair into a comment accordin 225 tag/value pair into a comment according to the placement
230 guidelines in the licensing rules docu 226 guidelines in the licensing rules documentation.
231 SPDX-License-Identifier: MIT 227 SPDX-License-Identifier: MIT
232 License-Text: 228 License-Text:
233 Full license text 229 Full license text
234 230
235 | 231 |
236 232
237 2. Deprecated licenses: !! 233 2. Not recommended licenses:
238 234
239 These licenses should only be used for exis 235 These licenses should only be used for existing code or for importing
240 code from a different project. These licen 236 code from a different project. These licenses are available from the
241 directory:: 237 directory::
242 238
243 LICENSES/deprecated/ !! 239 LICENSES/other/
244 240
245 in the kernel source tree. 241 in the kernel source tree.
246 242
247 The files in this directory contain the ful 243 The files in this directory contain the full license text and
248 `Metatags`_. The file names are identical 244 `Metatags`_. The file names are identical to the SPDX license
249 identifier which shall be used for the lice 245 identifier which shall be used for the license in source files.
250 246
251 Examples:: 247 Examples::
252 248
253 LICENSES/deprecated/ISC !! 249 LICENSES/other/ISC
254 250
255 Contains the Internet Systems Consortium li 251 Contains the Internet Systems Consortium license text and the required
256 metatags:: 252 metatags::
257 253
258 LICENSES/deprecated/GPL-1.0 !! 254 LICENSES/other/ZLib
259 255
260 Contains the GPL version 1 license text and !! 256 Contains the ZLIB license text and the required metatags.
261 257
262 Metatags: 258 Metatags:
263 259
264 The metatag requirements for 'other' licens 260 The metatag requirements for 'other' licenses are identical to the
265 requirements of the `Preferred licenses`_. 261 requirements of the `Preferred licenses`_.
266 262
267 File format example:: 263 File format example::
268 264
269 Valid-License-Identifier: ISC 265 Valid-License-Identifier: ISC
270 SPDX-URL: https://spdx.org/licenses/ISC. 266 SPDX-URL: https://spdx.org/licenses/ISC.html
271 Usage-Guide: 267 Usage-Guide:
272 Usage of this license in the kernel fo 268 Usage of this license in the kernel for new code is discouraged
273 and it should solely be used for impor 269 and it should solely be used for importing code from an already
274 existing project. 270 existing project.
275 To use this license in source code, pu 271 To use this license in source code, put the following SPDX
276 tag/value pair into a comment accordin 272 tag/value pair into a comment according to the placement
277 guidelines in the licensing rules docu 273 guidelines in the licensing rules documentation.
278 SPDX-License-Identifier: ISC 274 SPDX-License-Identifier: ISC
279 License-Text: 275 License-Text:
280 Full license text 276 Full license text
281 277
282 | 278 |
283 279
284 3. Dual Licensing Only !! 280 3. _`Exceptions`:
285 <<
286 These licenses should only be used to dual <<
287 license in addition to a preferred license. <<
288 from the directory:: <<
289 <<
290 LICENSES/dual/ <<
291 <<
292 in the kernel source tree. <<
293 <<
294 The files in this directory contain the ful <<
295 `Metatags`_. The file names are identical <<
296 identifier which shall be used for the lice <<
297 <<
298 Examples:: <<
299 <<
300 LICENSES/dual/MPL-1.1 <<
301 <<
302 Contains the Mozilla Public License version <<
303 required metatags:: <<
304 <<
305 LICENSES/dual/Apache-2.0 <<
306 <<
307 Contains the Apache License version 2.0 lic <<
308 metatags. <<
309 <<
310 Metatags: <<
311 <<
312 The metatag requirements for 'other' licens <<
313 requirements of the `Preferred licenses`_. <<
314 <<
315 File format example:: <<
316 <<
317 Valid-License-Identifier: MPL-1.1 <<
318 SPDX-URL: https://spdx.org/licenses/MPL- <<
319 Usage-Guide: <<
320 Do NOT use. The MPL-1.1 is not GPL2 co <<
321 dual-licensed files where the other li <<
322 If you end up using this it MUST be us <<
323 license using "OR". <<
324 To use the Mozilla Public License vers <<
325 tag/value pair into a comment accordin <<
326 the licensing rules documentation: <<
327 SPDX-License-Identifier: MPL-1.1 <<
328 License-Text: <<
329 Full license text <<
330 <<
331 | <<
332 <<
333 4. _`Exceptions`: <<
334 281
335 Some licenses can be amended with exception 282 Some licenses can be amended with exceptions which grant certain rights
336 which the original license does not. These 283 which the original license does not. These exceptions are available
337 from the directory:: 284 from the directory::
338 285
339 LICENSES/exceptions/ 286 LICENSES/exceptions/
340 287
341 in the kernel source tree. The files in th 288 in the kernel source tree. The files in this directory contain the full
342 exception text and the required `Exception 289 exception text and the required `Exception Metatags`_.
343 290
344 Examples:: 291 Examples::
345 292
346 LICENSES/exceptions/Linux-syscall-note 293 LICENSES/exceptions/Linux-syscall-note
347 294
348 Contains the Linux syscall exception as doc 295 Contains the Linux syscall exception as documented in the COPYING
349 file of the Linux kernel, which is used for 296 file of the Linux kernel, which is used for UAPI header files.
350 e.g. /\* SPDX-License-Identifier: GPL-2.0 W 297 e.g. /\* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note \*/::
351 298
352 LICENSES/exceptions/GCC-exception-2.0 299 LICENSES/exceptions/GCC-exception-2.0
353 300
354 Contains the GCC 'linking exception' which 301 Contains the GCC 'linking exception' which allows to link any binary
355 independent of its license against the comp 302 independent of its license against the compiled version of a file marked
356 with this exception. This is required for c 303 with this exception. This is required for creating runnable executables
357 from source code which is not compatible wi 304 from source code which is not compatible with the GPL.
358 305
359 _`Exception Metatags`: 306 _`Exception Metatags`:
360 307
361 The following meta tags must be available i 308 The following meta tags must be available in an exception file:
362 309
363 - SPDX-Exception-Identifier: 310 - SPDX-Exception-Identifier:
364 311
365 One exception identifier which can be use 312 One exception identifier which can be used with SPDX license
366 identifiers. 313 identifiers.
367 314
368 - SPDX-URL: 315 - SPDX-URL:
369 316
370 The URL of the SPDX page which contains a 317 The URL of the SPDX page which contains additional information related
371 to the exception. 318 to the exception.
372 319
373 - SPDX-Licenses: 320 - SPDX-Licenses:
374 321
375 A comma separated list of SPDX license id 322 A comma separated list of SPDX license identifiers for which the
376 exception can be used. 323 exception can be used.
377 324
378 - Usage-Guidance: 325 - Usage-Guidance:
379 326
380 Freeform text for usage advice. The text 327 Freeform text for usage advice. The text must be followed by correct
381 examples for the SPDX license identifiers 328 examples for the SPDX license identifiers as they should be put into
382 source files according to the `License id 329 source files according to the `License identifier syntax`_ guidelines.
383 330
384 - Exception-Text: 331 - Exception-Text:
385 332
386 All text after this tag is treated as the 333 All text after this tag is treated as the original exception text
387 334
388 File format examples:: 335 File format examples::
389 336
390 SPDX-Exception-Identifier: Linux-syscall 337 SPDX-Exception-Identifier: Linux-syscall-note
391 SPDX-URL: https://spdx.org/licenses/Linu 338 SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
392 SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1. 339 SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+
393 Usage-Guidance: 340 Usage-Guidance:
394 This exception is used together with o 341 This exception is used together with one of the above SPDX-Licenses
395 to mark user-space API (uapi) header f 342 to mark user-space API (uapi) header files so they can be included
396 into non GPL compliant user-space appl 343 into non GPL compliant user-space application code.
397 To use this exception add it with the 344 To use this exception add it with the keyword WITH to one of the
398 identifiers in the SPDX-Licenses tag: 345 identifiers in the SPDX-Licenses tag:
399 SPDX-License-Identifier: <SPDX-Licen 346 SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
400 Exception-Text: 347 Exception-Text:
401 Full exception text 348 Full exception text
402 349
403 :: 350 ::
404 351
405 SPDX-Exception-Identifier: GCC-exception 352 SPDX-Exception-Identifier: GCC-exception-2.0
406 SPDX-URL: https://spdx.org/licenses/GCC- 353 SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
407 SPDX-Licenses: GPL-2.0, GPL-2.0+ 354 SPDX-Licenses: GPL-2.0, GPL-2.0+
408 Usage-Guidance: 355 Usage-Guidance:
409 The "GCC Runtime Library exception 2.0 356 The "GCC Runtime Library exception 2.0" is used together with one
410 of the above SPDX-Licenses for code im 357 of the above SPDX-Licenses for code imported from the GCC runtime
411 library. 358 library.
412 To use this exception add it with the 359 To use this exception add it with the keyword WITH to one of the
413 identifiers in the SPDX-Licenses tag: 360 identifiers in the SPDX-Licenses tag:
414 SPDX-License-Identifier: <SPDX-Licen 361 SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
415 Exception-Text: 362 Exception-Text:
416 Full exception text 363 Full exception text
417 364
418 365
419 All SPDX license identifiers and exceptions mu 366 All SPDX license identifiers and exceptions must have a corresponding file
420 in the LICENSES subdirectories. This is requir !! 367 in the LICENSE subdirectories. This is required to allow tool
421 verification (e.g. checkpatch.pl) and to have 368 verification (e.g. checkpatch.pl) and to have the licenses ready to read
422 and extract right from the source, which is re 369 and extract right from the source, which is recommended by various FOSS
423 organizations, e.g. the `FSFE REUSE initiative 370 organizations, e.g. the `FSFE REUSE initiative <https://reuse.software/>`_.
424 <<
425 _`MODULE_LICENSE` <<
426 ----------------- <<
427 <<
428 Loadable kernel modules also require a MODU <<
429 neither a replacement for proper source cod <<
430 (SPDX-License-Identifier) nor in any way re <<
431 determining the exact license under which t <<
432 is provided. <<
433 <<
434 The sole purpose of this tag is to provide <<
435 whether the module is free software or prop <<
436 module loader and for user space tools. <<
437 <<
438 The valid license strings for MODULE_LICENS <<
439 <<
440 ============================= ============ <<
441 "GPL" Module is li <<
442 does not exp <<
443 GPL-2.0-only <<
444 license info <<
445 via the lice <<
446 correspondin <<
447 <<
448 "GPL v2" Same as "GPL <<
449 reasons. <<
450 <<
451 "GPL and additional rights" Historical v <<
452 module sourc <<
453 GPL v2 varia <<
454 not use in n <<
455 <<
456 "Dual MIT/GPL" The correct <<
457 module is du <<
458 variant or M <<
459 <<
460 "Dual BSD/GPL" The module i <<
461 variant or B <<
462 variant of t <<
463 determined v <<
464 in the corre <<
465 <<
466 "Dual MPL/GPL" The module i <<
467 variant or M <<
468 choice. The <<
469 license can <<
470 license info <<
471 source files <<
472 <<
473 "Proprietary" The module i <<
474 This string <<
475 party module <<
476 which have t <<
477 tree. Module <<
478 the kernel w <<
479 the kernel m <<
480 modules agai <<
481 with EXPORT_ <<
482 ============================= ============ <<
483 <<
484 <<
485 <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.