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