Lines Matching refs:license
14 should be annotated to make its license clear and unambiguous.
15 It doesn't replace the Kernel's license.
17 The license described in the COPYING file applies to the kernel source
18 as a whole, though individual source files can have a different license
28 Aside from that, individual files can be provided under a dual license,
30 permissive license like BSD, MIT etc.
38 kernel, the exception must be documented by a special license expression.
40 The common way of expressing the license of a source file is to add the
43 tools which are used in the context of license compliance.
46 Exchange (SPDX) license identifiers in each source file. SPDX license
47 identifiers are machine parsable and precise shorthands for the license
48 under which the content of the file is contributed. SPDX license
56 license list at https://spdx.org/licenses/ along with the license texts.
63 The SPDX license identifier in kernel files shall be added at the first
73 The SPDX license identifier is added in form of a comment. The comment
95 A <SPDX License Expression> is either an SPDX short form license
97 SPDX short form license identifiers separated by "WITH" when a license
108 WITH should be used when there is a modifier to a license needed.
124 OR should be used if the file is dual licensed and only one license is
130 Examples from the kernel for license expressions in dual licensed files::
142 original license terms need to remain in effect::
146 Another other example where both sets of license terms need to be
167 The files in this directory contain the full license text and
168 `Metatags`_. The file names are identical to the SPDX license
169 identifier which shall be used for the license in source files.
175 Contains the GPL version 2 license text and the required metatags::
179 Contains the MIT license text and the required metatags
183 The following meta tags must be available in a license file:
188 inside the project to reference this particular license text. Usually
195 to the license.
200 for the SPDX license identifiers as they should be put into source
205 All text after this tag is treated as the original license text
213 To use this license in source code, put one of the following SPDX
221 Full license text
228 To use this license in source code, put the following SPDX
233 Full license text
247 The files in this directory contain the full license text and
248 `Metatags`_. The file names are identical to the SPDX license
249 identifier which shall be used for the license in source files.
255 Contains the Internet Systems Consortium license text and the required
260 Contains the GPL version 1 license text and the required metatags.
272 Usage of this license in the kernel for new code is discouraged
275 To use this license in source code, put the following SPDX
280 Full license text
286 These licenses should only be used to dual license code with another
287 license in addition to a preferred license. These licenses are available
294 The files in this directory contain the full license text and
295 `Metatags`_. The file names are identical to the SPDX license
296 identifier which shall be used for the license in source files.
302 Contains the Mozilla Public License version 1.1 license text and the
307 Contains the Apache License version 2.0 license text and the required
321 dual-licensed files where the other license is GPL2 compatible.
323 license using "OR".
329 Full license text
336 which the original license does not. These exceptions are available
355 independent of its license against the compiled version of a file marked
365 One exception identifier which can be used with SPDX license
375 A comma separated list of SPDX license identifiers for which the
381 examples for the SPDX license identifiers as they should be put into
419 All SPDX license identifiers and exceptions must have a corresponding file
429 neither a replacement for proper source code license information
431 determining the exact license under which the source code of the module
438 The valid license strings for MODULE_LICENSE() are:
444 license information can only be determined
445 via the license information in the
453 GPL v2 variant and MIT license. Please do
458 variant or MIT license choice.
461 variant or BSD license choice. The exact
462 variant of the BSD license can only be
463 determined via the license information
469 license can only be determined via the
470 license information in the corresponding
473 "Proprietary" The module is under a proprietary license.