€•6      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ)/translations/zh_CN/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/zh_TW/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/it_IT/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ja_JP/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ko_KR/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/sp_SP/process/license-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒC/var/lib/git/docbuild/linux/Documentation/process/license-rules.rst”h KubhŒtarget”“”)”}”(hŒ.. _kernel_licensing:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œkernel-licensing”uh1h´h KhhhžhhŸh³ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒLinux kernel licensing rules”h]”hŒLinux kernel licensing rules”…””}”(hhÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhhÄhžhhŸh³h KubhŒ	paragraph”“”)”}”(hX  The Linux Kernel is provided under the terms of the GNU General Public
License version 2 only (GPL-2.0), as provided in LICENSES/preferred/GPL-2.0,
with an explicit syscall exception described in
LICENSES/exceptions/Linux-syscall-note, as described in the COPYING file.”h]”hX  The Linux Kernel is provided under the terms of the GNU General Public
License version 2 only (GPL-2.0), as provided in LICENSES/preferred/GPL-2.0,
with an explicit syscall exception described in
LICENSES/exceptions/Linux-syscall-note, as described in the COPYING file.”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hŒ®This documentation file provides a description of how each source file
should be annotated to make its license clear and unambiguous.
It doesn't replace the Kernel's license.”h]”hŒ²This documentation file provides a description of how each source file
should be annotated to make its license clear and unambiguous.
It doesnâ€™t replace the Kernelâ€™s license.”…””}”(hhçhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hŒÄThe license described in the COPYING file applies to the kernel source
as a whole, though individual source files can have a different license
which is required to be compatible with the GPL-2.0::”h]”hŒÃThe license described in the COPYING file applies to the kernel source
as a whole, though individual source files can have a different license
which is required to be compatible with the GPL-2.0:”…””}”(hhõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhŒliteral_block”“”)”}”(hXU  GPL-1.0+  :  GNU General Public License v1.0 or later
GPL-2.0+  :  GNU General Public License v2.0 or later
LGPL-2.0  :  GNU Library General Public License v2 only
LGPL-2.0+ :  GNU Library General Public License v2 or later
LGPL-2.1  :  GNU Lesser General Public License v2.1 only
LGPL-2.1+ :  GNU Lesser General Public License v2.1 or later”h]”hXU  GPL-1.0+  :  GNU General Public License v1.0 or later
GPL-2.0+  :  GNU General Public License v2.0 or later
LGPL-2.0  :  GNU Library General Public License v2 only
LGPL-2.0+ :  GNU Library General Public License v2 or later
LGPL-2.1  :  GNU Lesser General Public License v2.1 only
LGPL-2.1+ :  GNU Lesser General Public License v2.1 or later”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KhhÄhžhubhØ)”}”(hŒ¯Aside from that, individual files can be provided under a dual license,
e.g. one of the compatible GPL variants and alternatively under a
permissive license like BSD, MIT etc.”h]”hŒ¯Aside from that, individual files can be provided under a dual license,
e.g. one of the compatible GPL variants and alternatively under a
permissive license like BSD, MIT etc.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hX  The User-space API (UAPI) header files, which describe the interface of
user-space programs to the kernel are a special case.  According to the
note in the kernel COPYING file, the syscall interface is a clear boundary,
which does not extend the GPL requirements to any software which uses it to
communicate with the kernel.  Because the UAPI headers must be includable
into any source files which create an executable running on the Linux
kernel, the exception must be documented by a special license expression.”h]”hX  The User-space API (UAPI) header files, which describe the interface of
user-space programs to the kernel are a special case.  According to the
note in the kernel COPYING file, the syscall interface is a clear boundary,
which does not extend the GPL requirements to any software which uses it to
communicate with the kernel.  Because the UAPI headers must be includable
into any source files which create an executable running on the Linux
kernel, the exception must be documented by a special license expression.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K hhÄhžhubhØ)”}”(hX  The common way of expressing the license of a source file is to add the
matching boilerplate text into the top comment of the file.  Due to
formatting, typos etc. these "boilerplates" are hard to validate for
tools which are used in the context of license compliance.”h]”hX  The common way of expressing the license of a source file is to add the
matching boilerplate text into the top comment of the file.  Due to
formatting, typos etc. these â€œboilerplatesâ€ are hard to validate for
tools which are used in the context of license compliance.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K(hhÄhžhubhØ)”}”(hXè  An alternative to boilerplate text is the use of Software Package Data
Exchange (SPDX) license identifiers in each source file.  SPDX license
identifiers are machine parsable and precise shorthands for the license
under which the content of the file is contributed.  SPDX license
identifiers are managed by the SPDX Workgroup at the Linux Foundation and
have been agreed on by partners throughout the industry, tool vendors, and
legal teams.  For further information see https://spdx.org/”h]”(hX×  An alternative to boilerplate text is the use of Software Package Data
Exchange (SPDX) license identifiers in each source file.  SPDX license
identifiers are machine parsable and precise shorthands for the license
under which the content of the file is contributed.  SPDX license
identifiers are managed by the SPDX Workgroup at the Linux Foundation and
have been agreed on by partners throughout the industry, tool vendors, and
legal teams.  For further information see ”…””}”(hj=  hžhhŸNh NubhŒ	reference”“”)”}”(hŒhttps://spdx.org/”h]”hŒhttps://spdx.org/”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jI  uh1jE  hj=  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K-hhÄhžhubhØ)”}”(hX  The Linux kernel requires the precise SPDX identifier in all source files.
The valid identifiers used in the kernel are explained in the section
`License identifiers`_ and have been retrieved from the official SPDX
license list at https://spdx.org/licenses/ along with the license texts.”h]”(hŒ‘The Linux kernel requires the precise SPDX identifier in all source files.
The valid identifiers used in the kernel are explained in the section
”…””}”(hj\  hžhhŸNh NubjF  )”}”(hŒ`License identifiers`_”h]”hŒLicense identifiers”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLicense identifiers”hÀŒlicense-identifiers”uh1jE  hj\  Œresolved”KubhŒ@ and have been retrieved from the official SPDX
license list at ”…””}”(hj\  hžhhŸNh NubjF  )”}”(hŒhttps://spdx.org/licenses/”h]”hŒhttps://spdx.org/licenses/”…””}”(hjz  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j|  uh1jE  hj\  ubhŒ along with the license texts.”…””}”(hj\  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K5hhÄhžhubhÃ)”}”(hhh]”(hÈ)”}”(hŒLicense identifier syntax”h]”hŒLicense identifier syntax”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj“  hžhhŸh³h K;ubhŒenumerated_list”“”)”}”(hhh]”hŒ	list_item”“”)”}”(hXN  Placement:

The SPDX license identifier in kernel files shall be added at the first
possible line in a file which can contain a comment.  For the majority
of files this is the first line, except for scripts which require the
'#!PATH_TO_INTERPRETER' in the first line.  For those scripts the SPDX
identifier goes into the second line.
”h]”(hØ)”}”(hŒ
Placement:”h]”hŒ
Placement:”…””}”(hj¯  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K=hj«  ubhØ)”}”(hXA  The SPDX license identifier in kernel files shall be added at the first
possible line in a file which can contain a comment.  For the majority
of files this is the first line, except for scripts which require the
'#!PATH_TO_INTERPRETER' in the first line.  For those scripts the SPDX
identifier goes into the second line.”h]”hXE  The SPDX license identifier in kernel files shall be added at the first
possible line in a file which can contain a comment.  For the majority
of files this is the first line, except for scripts which require the
â€˜#!PATH_TO_INTERPRETERâ€™ in the first line.  For those scripts the SPDX
identifier goes into the second line.”…””}”(hj½  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K?hj«  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj¦  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1j¤  hj“  hžhhŸh³h K=ubhŒ
line_block”“”)”}”(hhh]”hh “”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hjÞ  hžhhŸh³h K Œindent”K ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜ  hj“  hžhhŸh³h KEubj¥  )”}”(hhh]”jª  )”}”(hX·  Style:

The SPDX license identifier is added in form of a comment.  The comment
style depends on the file type::

   C source: // SPDX-License-Identifier: <SPDX License Expression>
   C header: /* SPDX-License-Identifier: <SPDX License Expression> */
   ASM:      /* SPDX-License-Identifier: <SPDX License Expression> */
   scripts:  # SPDX-License-Identifier: <SPDX License Expression>
   .rst:     .. SPDX-License-Identifier: <SPDX License Expression>
   .dts{i}:  // SPDX-License-Identifier: <SPDX License Expression>

If a specific tool cannot handle the standard comment style, then the
appropriate comment mechanism which the tool accepts shall be used. This
is the reason for having the "/\* \*/" style comment in C header
files. There was build breakage observed with generated .lds files where
'ld' failed to parse the C++ comment. This has been fixed by now, but
there are still older assembler tools which cannot handle C++ style
comments.
”h]”(hØ)”}”(hŒStyle:”h]”hŒStyle:”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KGhjõ  ubhØ)”}”(hŒhThe SPDX license identifier is added in form of a comment.  The comment
style depends on the file type::”h]”hŒgThe SPDX license identifier is added in form of a comment.  The comment
style depends on the file type:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KIhjõ  ubj  )”}”(hX„  C source: // SPDX-License-Identifier: <SPDX License Expression>
C header: /* SPDX-License-Identifier: <SPDX License Expression> */
ASM:      /* SPDX-License-Identifier: <SPDX License Expression> */
scripts:  # SPDX-License-Identifier: <SPDX License Expression>
.rst:     .. SPDX-License-Identifier: <SPDX License Expression>
.dts{i}:  // SPDX-License-Identifier: <SPDX License Expression>”h]”hX„  C source: // SPDX-License-Identifier: <SPDX License Expression>
C header: /* SPDX-License-Identifier: <SPDX License Expression> */
ASM:      /* SPDX-License-Identifier: <SPDX License Expression> */
scripts:  # SPDX-License-Identifier: <SPDX License Expression>
.rst:     .. SPDX-License-Identifier: <SPDX License Expression>
.dts{i}:  // SPDX-License-Identifier: <SPDX License Expression>”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KLhjõ  ubhØ)”}”(hX¬  If a specific tool cannot handle the standard comment style, then the
appropriate comment mechanism which the tool accepts shall be used. This
is the reason for having the "/\* \*/" style comment in C header
files. There was build breakage observed with generated .lds files where
'ld' failed to parse the C++ comment. This has been fixed by now, but
there are still older assembler tools which cannot handle C++ style
comments.”h]”hX´  If a specific tool cannot handle the standard comment style, then the
appropriate comment mechanism which the tool accepts shall be used. This
is the reason for having the â€œ/ *  */â€ style comment in C header
files. There was build breakage observed with generated .lds files where
â€˜ldâ€™ failed to parse the C++ comment. This has been fixed by now, but
there are still older assembler tools which cannot handle C++ style
comments.”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KShjõ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hjò  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  Œstart”Kuh1j¤  hj“  hžhhŸh³h KGubjÝ  )”}”(hhh]”já  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hj>  hžhhŸh³h K jë  K ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜ  hj“  hžhhŸh³h K[ubj¥  )”}”(hhh]”jª  )”}”(hX;	  Syntax:

A <SPDX License Expression> is either an SPDX short form license
identifier found on the SPDX License List, or the combination of two
SPDX short form license identifiers separated by "WITH" when a license
exception applies. When multiple licenses apply, an expression consists
of keywords "AND", "OR" separating sub-expressions and surrounded by
"(", ")" .

License identifiers for licenses like [L]GPL with the 'or later' option
are constructed by using a "+" for indicating the 'or later' option.::

   // SPDX-License-Identifier: GPL-2.0+
   // SPDX-License-Identifier: LGPL-2.1+

WITH should be used when there is a modifier to a license needed.
For example, the linux kernel UAPI files use the expression::

   // SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
   // SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note

Other examples using WITH exceptions found in the kernel are::

   // SPDX-License-Identifier: GPL-2.0 WITH mif-exception
   // SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0

Exceptions can only be used with particular License identifiers. The
valid License identifiers are listed in the tags of the exception text
file. For details see the point `Exceptions`_ in the chapter `License
identifiers`_.

OR should be used if the file is dual licensed and only one license is
to be selected.  For example, some dtsi files are available under dual
licenses::

   // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause

Examples from the kernel for license expressions in dual licensed files::

   // SPDX-License-Identifier: GPL-2.0 OR MIT
   // SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
   // SPDX-License-Identifier: GPL-2.0 OR Apache-2.0
   // SPDX-License-Identifier: GPL-2.0 OR MPL-1.1
   // SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) OR MIT
   // SPDX-License-Identifier: GPL-1.0+ OR BSD-3-Clause OR OpenSSL

AND should be used if the file has multiple licenses whose terms all
apply to use the file. For example, if code is inherited from another
project and permission has been given to put it in the kernel, but the
original license terms need to remain in effect::

   // SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) AND MIT

Another other example where both sets of license terms need to be
adhered to is::

   // SPDX-License-Identifier: GPL-1.0+ AND LGPL-2.1+
”h]”(hØ)”}”(hŒSyntax:”h]”hŒSyntax:”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K]hjS  ubhØ)”}”(hXd  A <SPDX License Expression> is either an SPDX short form license
identifier found on the SPDX License List, or the combination of two
SPDX short form license identifiers separated by "WITH" when a license
exception applies. When multiple licenses apply, an expression consists
of keywords "AND", "OR" separating sub-expressions and surrounded by
"(", ")" .”h]”hXx  A <SPDX License Expression> is either an SPDX short form license
identifier found on the SPDX License List, or the combination of two
SPDX short form license identifiers separated by â€œWITHâ€ when a license
exception applies. When multiple licenses apply, an expression consists
of keywords â€œANDâ€, â€œORâ€ separating sub-expressions and surrounded by
â€œ(â€, â€œ)â€ .”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K_hjS  ubhØ)”}”(hŒŽLicense identifiers for licenses like [L]GPL with the 'or later' option
are constructed by using a "+" for indicating the 'or later' option.::”h]”hŒ™License identifiers for licenses like [L]GPL with the â€˜or laterâ€™ option
are constructed by using a â€œ+â€ for indicating the â€˜or laterâ€™ option.:”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KfhjS  ubj  )”}”(hŒJ// SPDX-License-Identifier: GPL-2.0+
// SPDX-License-Identifier: LGPL-2.1+”h]”hŒJ// SPDX-License-Identifier: GPL-2.0+
// SPDX-License-Identifier: LGPL-2.1+”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KihjS  ubhØ)”}”(hŒWITH should be used when there is a modifier to a license needed.
For example, the linux kernel UAPI files use the expression::”h]”hŒ~WITH should be used when there is a modifier to a license needed.
For example, the linux kernel UAPI files use the expression:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KlhjS  ubj  )”}”(hŒx// SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
// SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note”h]”hŒx// SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
// SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KohjS  ubhØ)”}”(hŒ>Other examples using WITH exceptions found in the kernel are::”h]”hŒ=Other examples using WITH exceptions found in the kernel are:”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KrhjS  ubj  )”}”(hŒr// SPDX-License-Identifier: GPL-2.0 WITH mif-exception
// SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0”h]”hŒr// SPDX-License-Identifier: GPL-2.0 WITH mif-exception
// SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0”…””}”hj¹  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KthjS  ubhØ)”}”(hŒàExceptions can only be used with particular License identifiers. The
valid License identifiers are listed in the tags of the exception text
file. For details see the point `Exceptions`_ in the chapter `License
identifiers`_.”h]”(hŒ¬Exceptions can only be used with particular License identifiers. The
valid License identifiers are listed in the tags of the exception text
file. For details see the point ”…””}”(hjÇ  hžhhŸNh NubjF  )”}”(hŒ`Exceptions`_”h]”hŒ
Exceptions”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ
Exceptions”hÀŒ
exceptions”uh1jE  hjÇ  ju  KubhŒ in the chapter ”…””}”(hjÇ  hžhhŸNh NubjF  )”}”(hŒ`License
identifiers`_”h]”hŒLicense
identifiers”…””}”(hjä  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLicense identifiers”hÀjt  uh1jE  hjÇ  ju  KubhŒ.”…””}”(hjÇ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KwhjS  ubhØ)”}”(hŒ˜OR should be used if the file is dual licensed and only one license is
to be selected.  For example, some dtsi files are available under dual
licenses::”h]”hŒ—OR should be used if the file is dual licensed and only one license is
to be selected.  For example, some dtsi files are available under dual
licenses:”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K|hjS  ubj  )”}”(hŒ3// SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause”h]”hŒ3// SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K€hjS  ubhØ)”}”(hŒIExamples from the kernel for license expressions in dual licensed files::”h]”hŒHExamples from the kernel for license expressions in dual licensed files:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K‚hjS  ubj  )”}”(hXD  // SPDX-License-Identifier: GPL-2.0 OR MIT
// SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
// SPDX-License-Identifier: GPL-2.0 OR Apache-2.0
// SPDX-License-Identifier: GPL-2.0 OR MPL-1.1
// SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) OR MIT
// SPDX-License-Identifier: GPL-1.0+ OR BSD-3-Clause OR OpenSSL”h]”hXD  // SPDX-License-Identifier: GPL-2.0 OR MIT
// SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
// SPDX-License-Identifier: GPL-2.0 OR Apache-2.0
// SPDX-License-Identifier: GPL-2.0 OR MPL-1.1
// SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) OR MIT
// SPDX-License-Identifier: GPL-1.0+ OR BSD-3-Clause OR OpenSSL”…””}”hj(  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K„hjS  ubhØ)”}”(hX  AND should be used if the file has multiple licenses whose terms all
apply to use the file. For example, if code is inherited from another
project and permission has been given to put it in the kernel, but the
original license terms need to remain in effect::”h]”hX  AND should be used if the file has multiple licenses whose terms all
apply to use the file. For example, if code is inherited from another
project and permission has been given to put it in the kernel, but the
original license terms need to remain in effect:”…””}”(hj6  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K‹hjS  ubj  )”}”(hŒE// SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) AND MIT”h]”hŒE// SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) AND MIT”…””}”hjD  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KhjS  ubhØ)”}”(hŒQAnother other example where both sets of license terms need to be
adhered to is::”h]”hŒPAnother other example where both sets of license terms need to be
adhered to is:”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K’hjS  ubj  )”}”(hŒ2// SPDX-License-Identifier: GPL-1.0+ AND LGPL-2.1+”h]”hŒ2// SPDX-License-Identifier: GPL-1.0+ AND LGPL-2.1+”…””}”hj`  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K•hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hjP  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  j=  Kuh1j¤  hj“  hžhhŸh³h K]ubeh}”(h]”Œlicense-identifier-syntax”ah ]”h"]”Œlicense identifier syntax”ah$]”h&]”uh1hÂhhÄhžhhŸh³h K;Œ
referenced”KubhÃ)”}”(hhh]”(hÈ)”}”(hŒLicense identifiers”h]”hŒLicense identifiers”…””}”(hj†  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjƒ  hžhhŸh³h K˜ubhØ)”}”(hŒkThe licenses currently used, as well as the licenses for code added to the
kernel, can be broken down into:”h]”hŒkThe licenses currently used, as well as the licenses for code added to the
kernel, can be broken down into:”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kšhjƒ  hžhubj¥  )”}”(hhh]”jª  )”}”(hXK	  _`Preferred licenses`:

Whenever possible these licenses should be used as they are known to be
fully compatible and widely used.  These licenses are available from the
directory::

   LICENSES/preferred/

in the kernel source tree.

The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.

Examples::

   LICENSES/preferred/GPL-2.0

Contains the GPL version 2 license text and the required metatags::

   LICENSES/preferred/MIT

Contains the MIT license text and the required metatags

_`Metatags`:

The following meta tags must be available in a license file:

- Valid-License-Identifier:

  One or more lines which declare which License Identifiers are valid
  inside the project to reference this particular license text.  Usually
  this is a single valid identifier, but e.g. for licenses with the 'or
  later' options two identifiers are valid.

- SPDX-URL:

  The URL of the SPDX page which contains additional information related
  to the license.

- Usage-Guidance:

  Freeform text for usage advice. The text must include correct examples
  for the SPDX license identifiers as they should be put into source
  files according to the `License identifier syntax`_ guidelines.

- License-Text:

  All text after this tag is treated as the original license text

File format examples::

   Valid-License-Identifier: GPL-2.0
   Valid-License-Identifier: GPL-2.0+
   SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
   Usage-Guide:
     To use this license in source code, put one of the following SPDX
     tag/value pairs into a comment according to the placement
     guidelines in the licensing rules documentation.
     For 'GNU General Public License (GPL) version 2 only' use:
       SPDX-License-Identifier: GPL-2.0
     For 'GNU General Public License (GPL) version 2 or any later version' use:
       SPDX-License-Identifier: GPL-2.0+
   License-Text:
     Full license text

::

   SPDX-License-Identifier: MIT
   SPDX-URL: https://spdx.org/licenses/MIT.html
   Usage-Guide:
     To use this license in source code, put the following SPDX
     tag/value pair into a comment according to the placement
     guidelines in the licensing rules documentation.
       SPDX-License-Identifier: MIT
   License-Text:
     Full license text
”h]”(hØ)”}”(hŒ_`Preferred licenses`:”h]”(hµ)”}”(hŒ_`Preferred licenses`”h]”hŒPreferred licenses”…””}”(hj­  hžhhŸNh Nubah}”(h]”Œpreferred-licenses”ah ]”h"]”Œpreferred licenses”ah$]”h&]”uh1h´hj©  j‚  KubhŒ:”…””}”(hj©  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj¥  ubhØ)”}”(hŒœWhenever possible these licenses should be used as they are known to be
fully compatible and widely used.  These licenses are available from the
directory::”h]”hŒ›Whenever possible these licenses should be used as they are known to be
fully compatible and widely used.  These licenses are available from the
directory:”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KŸhj¥  ubj  )”}”(hŒLICENSES/preferred/”h]”hŒLICENSES/preferred/”…””}”hjÕ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K£hj¥  ubhØ)”}”(hŒin the kernel source tree.”h]”hŒin the kernel source tree.”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K¥hj¥  ubhØ)”}”(hŒ¼The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”h]”(hŒ>The files in this directory contain the full license text and
”…””}”(hjñ  hžhhŸNh NubjF  )”}”(hŒ`Metatags`_”h]”hŒMetatags”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒMetatags”hÀŒmetatags”uh1jE  hjñ  ju  KubhŒs.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”…””}”(hjñ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K§hj¥  ubhØ)”}”(hŒ
Examples::”h]”hŒ	Examples:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K«hj¥  ubj  )”}”(hŒLICENSES/preferred/GPL-2.0”h]”hŒLICENSES/preferred/GPL-2.0”…””}”hj"  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K­hj¥  ubhØ)”}”(hŒCContains the GPL version 2 license text and the required metatags::”h]”hŒBContains the GPL version 2 license text and the required metatags:”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K¯hj¥  ubj  )”}”(hŒLICENSES/preferred/MIT”h]”hŒLICENSES/preferred/MIT”…””}”hj>  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K±hj¥  ubhØ)”}”(hŒ7Contains the MIT license text and the required metatags”h]”hŒ7Contains the MIT license text and the required metatags”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K³hj¥  ubhØ)”}”(hŒ_`Metatags`:”h]”(hµ)”}”(hŒ_`Metatags`”h]”hŒMetatags”…””}”(hj^  hžhhŸNh Nubah}”(h]”j	  ah ]”h"]”Œmetatags”ah$]”h&]”uh1h´hjZ  j‚  KubhŒ:”…””}”(hjZ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kµhj¥  ubhØ)”}”(hŒ<The following meta tags must be available in a license file:”h]”hŒ<The following meta tags must be available in a license file:”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K·hj¥  ubhŒbullet_list”“”)”}”(hhh]”(jª  )”}”(hX  Valid-License-Identifier:

One or more lines which declare which License Identifiers are valid
inside the project to reference this particular license text.  Usually
this is a single valid identifier, but e.g. for licenses with the 'or
later' options two identifiers are valid.
”h]”(hØ)”}”(hŒValid-License-Identifier:”h]”hŒValid-License-Identifier:”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K¹hjŠ  ubhØ)”}”(hŒúOne or more lines which declare which License Identifiers are valid
inside the project to reference this particular license text.  Usually
this is a single valid identifier, but e.g. for licenses with the 'or
later' options two identifiers are valid.”h]”hŒþOne or more lines which declare which License Identifiers are valid
inside the project to reference this particular license text.  Usually
this is a single valid identifier, but e.g. for licenses with the â€˜or
laterâ€™ options two identifiers are valid.”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K»hjŠ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj‡  ubjª  )”}”(hŒbSPDX-URL:

The URL of the SPDX page which contains additional information related
to the license.
”h]”(hØ)”}”(hŒ	SPDX-URL:”h]”hŒ	SPDX-URL:”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÀhj°  ubhØ)”}”(hŒVThe URL of the SPDX page which contains additional information related
to the license.”h]”hŒVThe URL of the SPDX page which contains additional information related
to the license.”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÂhj°  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj‡  ubjª  )”}”(hŒÛUsage-Guidance:

Freeform text for usage advice. The text must include correct examples
for the SPDX license identifiers as they should be put into source
files according to the `License identifier syntax`_ guidelines.
”h]”(hØ)”}”(hŒUsage-Guidance:”h]”hŒUsage-Guidance:”…””}”(hjÚ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÅhjÖ  ubhØ)”}”(hŒÉFreeform text for usage advice. The text must include correct examples
for the SPDX license identifiers as they should be put into source
files according to the `License identifier syntax`_ guidelines.”h]”(hŒ¡Freeform text for usage advice. The text must include correct examples
for the SPDX license identifiers as they should be put into source
files according to the ”…””}”(hjè  hžhhŸNh NubjF  )”}”(hŒ`License identifier syntax`_”h]”hŒLicense identifier syntax”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLicense identifier syntax”hÀj|  uh1jE  hjè  ju  KubhŒ guidelines.”…””}”(hjè  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÇhjÖ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj‡  ubjª  )”}”(hŒOLicense-Text:

All text after this tag is treated as the original license text
”h]”(hØ)”}”(hŒLicense-Text:”h]”hŒLicense-Text:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KËhj  ubhØ)”}”(hŒ?All text after this tag is treated as the original license text”h]”hŒ?All text after this tag is treated as the original license text”…””}”(hj"  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÍhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj‡  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1j…  hŸh³h K¹hj¥  ubhØ)”}”(hŒFile format examples::”h]”hŒFile format examples:”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÏhj¥  ubj  )”}”(hX,  Valid-License-Identifier: GPL-2.0
Valid-License-Identifier: GPL-2.0+
SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
Usage-Guide:
  To use this license in source code, put one of the following SPDX
  tag/value pairs into a comment according to the placement
  guidelines in the licensing rules documentation.
  For 'GNU General Public License (GPL) version 2 only' use:
    SPDX-License-Identifier: GPL-2.0
  For 'GNU General Public License (GPL) version 2 or any later version' use:
    SPDX-License-Identifier: GPL-2.0+
License-Text:
  Full license text”h]”hX,  Valid-License-Identifier: GPL-2.0
Valid-License-Identifier: GPL-2.0+
SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
Usage-Guide:
  To use this license in source code, put one of the following SPDX
  tag/value pairs into a comment according to the placement
  guidelines in the licensing rules documentation.
  For 'GNU General Public License (GPL) version 2 only' use:
    SPDX-License-Identifier: GPL-2.0
  For 'GNU General Public License (GPL) version 2 or any later version' use:
    SPDX-License-Identifier: GPL-2.0+
License-Text:
  Full license text”…””}”hjL  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KÑhj¥  ubj  )”}”(hXD  SPDX-License-Identifier: MIT
SPDX-URL: https://spdx.org/licenses/MIT.html
Usage-Guide:
  To use this license in source code, put the following SPDX
  tag/value pair into a comment according to the placement
  guidelines in the licensing rules documentation.
    SPDX-License-Identifier: MIT
License-Text:
  Full license text”h]”hXD  SPDX-License-Identifier: MIT
SPDX-URL: https://spdx.org/licenses/MIT.html
Usage-Guide:
  To use this license in source code, put the following SPDX
  tag/value pair into a comment according to the placement
  guidelines in the licensing rules documentation.
    SPDX-License-Identifier: MIT
License-Text:
  Full license text”…””}”hjZ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Káhj¥  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj¢  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  uh1j¤  hjƒ  hžhhŸh³h KubjÝ  )”}”(hhh]”já  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hjt  hžhhŸh³h K jë  K ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜ  hjƒ  hžhhŸh³h Këubj¥  )”}”(hhh]”jª  )”}”(hX  Deprecated licenses:

These licenses should only be used for existing code or for importing
code from a different project.  These licenses are available from the
directory::

   LICENSES/deprecated/

in the kernel source tree.

The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.

Examples::

   LICENSES/deprecated/ISC

Contains the Internet Systems Consortium license text and the required
metatags::

   LICENSES/deprecated/GPL-1.0

Contains the GPL version 1 license text and the required metatags.

Metatags:

The metatag requirements for 'other' licenses are identical to the
requirements of the `Preferred licenses`_.

File format example::

   Valid-License-Identifier: ISC
   SPDX-URL: https://spdx.org/licenses/ISC.html
   Usage-Guide:
     Usage of this license in the kernel for new code is discouraged
     and it should solely be used for importing code from an already
     existing project.
     To use this license in source code, put the following SPDX
     tag/value pair into a comment according to the placement
     guidelines in the licensing rules documentation.
       SPDX-License-Identifier: ISC
   License-Text:
     Full license text
”h]”(hØ)”}”(hŒDeprecated licenses:”h]”hŒDeprecated licenses:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kíhj‰  ubhØ)”}”(hŒ—These licenses should only be used for existing code or for importing
code from a different project.  These licenses are available from the
directory::”h]”hŒ–These licenses should only be used for existing code or for importing
code from a different project.  These licenses are available from the
directory:”…””}”(hj›  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kïhj‰  ubj  )”}”(hŒLICENSES/deprecated/”h]”hŒLICENSES/deprecated/”…””}”hj©  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Kóhj‰  ubhØ)”}”(hŒin the kernel source tree.”h]”hŒin the kernel source tree.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kõhj‰  ubhØ)”}”(hŒ¼The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”h]”(hŒ>The files in this directory contain the full license text and
”…””}”(hjÅ  hžhhŸNh NubjF  )”}”(hŒ`Metatags`_”h]”hŒMetatags”…””}”(hjÍ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒMetatags”hÀj	  uh1jE  hjÅ  ju  KubhŒs.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”…””}”(hjÅ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K÷hj‰  ubhØ)”}”(hŒ
Examples::”h]”hŒ	Examples:”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kûhj‰  ubj  )”}”(hŒLICENSES/deprecated/ISC”h]”hŒLICENSES/deprecated/ISC”…””}”hjõ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Kýhj‰  ubhØ)”}”(hŒQContains the Internet Systems Consortium license text and the required
metatags::”h]”hŒPContains the Internet Systems Consortium license text and the required
metatags:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kÿhj‰  ubj  )”}”(hŒLICENSES/deprecated/GPL-1.0”h]”hŒLICENSES/deprecated/GPL-1.0”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Mhj‰  ubhØ)”}”(hŒBContains the GPL version 1 license text and the required metatags.”h]”hŒBContains the GPL version 1 license text and the required metatags.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj‰  ubhØ)”}”(hŒ	Metatags:”h]”hŒ	Metatags:”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj‰  ubhØ)”}”(hŒmThe metatag requirements for 'other' licenses are identical to the
requirements of the `Preferred licenses`_.”h]”(hŒ[The metatag requirements for â€˜otherâ€™ licenses are identical to the
requirements of the ”…””}”(hj;  hžhhŸNh NubjF  )”}”(hŒ`Preferred licenses`_”h]”hŒPreferred licenses”…””}”(hjC  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒPreferred licenses”hÀj·  uh1jE  hj;  ju  KubhŒ.”…””}”(hj;  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj‰  ubhØ)”}”(hŒFile format example::”h]”hŒFile format example:”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj‰  ubj  )”}”(hXÝ  Valid-License-Identifier: ISC
SPDX-URL: https://spdx.org/licenses/ISC.html
Usage-Guide:
  Usage of this license in the kernel for new code is discouraged
  and it should solely be used for importing code from an already
  existing project.
  To use this license in source code, put the following SPDX
  tag/value pair into a comment according to the placement
  guidelines in the licensing rules documentation.
    SPDX-License-Identifier: ISC
License-Text:
  Full license text”h]”hXÝ  Valid-License-Identifier: ISC
SPDX-URL: https://spdx.org/licenses/ISC.html
Usage-Guide:
  Usage of this license in the kernel for new code is discouraged
  and it should solely be used for importing code from an already
  existing project.
  To use this license in source code, put the following SPDX
  tag/value pair into a comment according to the placement
  guidelines in the licensing rules documentation.
    SPDX-License-Identifier: ISC
License-Text:
  Full license text”…””}”hjk  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Mhj‰  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj†  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  j=  Kuh1j¤  hjƒ  hžhhŸh³h KíubjÝ  )”}”(hhh]”já  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hj…  hžhhŸh³h K jë  K ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜ  hjƒ  hžhhŸh³h Mubj¥  )”}”(hhh]”jª  )”}”(hX’  Dual Licensing Only

These licenses should only be used to dual license code with another
license in addition to a preferred license.  These licenses are available
from the directory::

   LICENSES/dual/

in the kernel source tree.

The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.

Examples::

   LICENSES/dual/MPL-1.1

Contains the Mozilla Public License version 1.1 license text and the
required metatags::

   LICENSES/dual/Apache-2.0

Contains the Apache License version 2.0 license text and the required
metatags.

Metatags:

The metatag requirements for 'other' licenses are identical to the
requirements of the `Preferred licenses`_.

File format example::

   Valid-License-Identifier: MPL-1.1
   SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
   Usage-Guide:
     Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used for
     dual-licensed files where the other license is GPL2 compatible.
     If you end up using this it MUST be used together with a GPL2 compatible
     license using "OR".
     To use the Mozilla Public License version 1.1 put the following SPDX
     tag/value pair into a comment according to the placement guidelines in
     the licensing rules documentation:
   SPDX-License-Identifier: MPL-1.1
   License-Text:
     Full license text
”h]”(hØ)”}”(hŒDual Licensing Only”h]”hŒDual Licensing Only”…””}”(hjž  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhjš  ubhØ)”}”(hŒ£These licenses should only be used to dual license code with another
license in addition to a preferred license.  These licenses are available
from the directory::”h]”hŒ¢These licenses should only be used to dual license code with another
license in addition to a preferred license.  These licenses are available
from the directory:”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhjš  ubj  )”}”(hŒLICENSES/dual/”h]”hŒLICENSES/dual/”…””}”hjº  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M"hjš  ubhØ)”}”(hŒin the kernel source tree.”h]”hŒin the kernel source tree.”…””}”(hjÈ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M$hjš  ubhØ)”}”(hŒ¼The files in this directory contain the full license text and
`Metatags`_.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”h]”(hŒ>The files in this directory contain the full license text and
”…””}”(hjÖ  hžhhŸNh NubjF  )”}”(hŒ`Metatags`_”h]”hŒMetatags”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒMetatags”hÀj	  uh1jE  hjÖ  ju  KubhŒs.  The file names are identical to the SPDX license
identifier which shall be used for the license in source files.”…””}”(hjÖ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M&hjš  ubhØ)”}”(hŒ
Examples::”h]”hŒ	Examples:”…””}”(hjø  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M*hjš  ubj  )”}”(hŒLICENSES/dual/MPL-1.1”h]”hŒLICENSES/dual/MPL-1.1”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M,hjš  ubhØ)”}”(hŒXContains the Mozilla Public License version 1.1 license text and the
required metatags::”h]”hŒWContains the Mozilla Public License version 1.1 license text and the
required metatags:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M.hjš  ubj  )”}”(hŒLICENSES/dual/Apache-2.0”h]”hŒLICENSES/dual/Apache-2.0”…””}”hj"  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M1hjš  ubhØ)”}”(hŒOContains the Apache License version 2.0 license text and the required
metatags.”h]”hŒOContains the Apache License version 2.0 license text and the required
metatags.”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M3hjš  ubhØ)”}”(hŒ	Metatags:”h]”hŒ	Metatags:”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M6hjš  ubhØ)”}”(hŒmThe metatag requirements for 'other' licenses are identical to the
requirements of the `Preferred licenses`_.”h]”(hŒ[The metatag requirements for â€˜otherâ€™ licenses are identical to the
requirements of the ”…””}”(hjL  hžhhŸNh NubjF  )”}”(hŒ`Preferred licenses`_”h]”hŒPreferred licenses”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒPreferred licenses”hÀj·  uh1jE  hjL  ju  KubhŒ.”…””}”(hjL  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M8hjš  ubhØ)”}”(hŒFile format example::”h]”hŒFile format example:”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M;hjš  ubj  )”}”(hXD  Valid-License-Identifier: MPL-1.1
SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
Usage-Guide:
  Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used for
  dual-licensed files where the other license is GPL2 compatible.
  If you end up using this it MUST be used together with a GPL2 compatible
  license using "OR".
  To use the Mozilla Public License version 1.1 put the following SPDX
  tag/value pair into a comment according to the placement guidelines in
  the licensing rules documentation:
SPDX-License-Identifier: MPL-1.1
License-Text:
  Full license text”h]”hXD  Valid-License-Identifier: MPL-1.1
SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
Usage-Guide:
  Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used for
  dual-licensed files where the other license is GPL2 compatible.
  If you end up using this it MUST be used together with a GPL2 compatible
  license using "OR".
  To use the Mozilla Public License version 1.1 put the following SPDX
  tag/value pair into a comment according to the placement guidelines in
  the licensing rules documentation:
SPDX-License-Identifier: MPL-1.1
License-Text:
  Full license text”…””}”hj|  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M=hjš  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj—  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  j=  Kuh1j¤  hjƒ  hžhhŸh³h MubjÝ  )”}”(hhh]”já  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hj–  hžhhŸh³h K jë  K ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜ  hjƒ  hžhhŸh³h MKubj¥  )”}”(hhh]”jª  )”}”(hX4  _`Exceptions`:

Some licenses can be amended with exceptions which grant certain rights
which the original license does not.  These exceptions are available
from the directory::

   LICENSES/exceptions/

in the kernel source tree.  The files in this directory contain the full
exception text and the required `Exception Metatags`_.

Examples::

   LICENSES/exceptions/Linux-syscall-note

Contains the Linux syscall exception as documented in the COPYING
file of the Linux kernel, which is used for UAPI header files.
e.g. /\* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note \*/::

   LICENSES/exceptions/GCC-exception-2.0

Contains the GCC 'linking exception' which allows to link any binary
independent of its license against the compiled version of a file marked
with this exception. This is required for creating runnable executables
from source code which is not compatible with the GPL.

_`Exception Metatags`:

The following meta tags must be available in an exception file:

- SPDX-Exception-Identifier:

  One exception identifier which can be used with SPDX license
  identifiers.

- SPDX-URL:

  The URL of the SPDX page which contains additional information related
  to the exception.

- SPDX-Licenses:

  A comma separated list of SPDX license identifiers for which the
  exception can be used.

- Usage-Guidance:

  Freeform text for usage advice. The text must be followed by correct
  examples for the SPDX license identifiers as they should be put into
  source files according to the `License identifier syntax`_ guidelines.

- Exception-Text:

  All text after this tag is treated as the original exception text

File format examples::

   SPDX-Exception-Identifier: Linux-syscall-note
   SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
   SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+
   Usage-Guidance:
     This exception is used together with one of the above SPDX-Licenses
     to mark user-space API (uapi) header files so they can be included
     into non GPL compliant user-space application code.
     To use this exception add it with the keyword WITH to one of the
     identifiers in the SPDX-Licenses tag:
       SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
   Exception-Text:
     Full exception text

::

   SPDX-Exception-Identifier: GCC-exception-2.0
   SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
   SPDX-Licenses: GPL-2.0, GPL-2.0+
   Usage-Guidance:
     The "GCC Runtime Library exception 2.0" is used together with one
     of the above SPDX-Licenses for code imported from the GCC runtime
     library.
     To use this exception add it with the keyword WITH to one of the
     identifiers in the SPDX-Licenses tag:
       SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
   Exception-Text:
     Full exception text

”h]”(hØ)”}”(hŒ_`Exceptions`:”h]”(hµ)”}”(hŒ_`Exceptions`”h]”hŒ
Exceptions”…””}”(hj³  hžhhŸNh Nubah}”(h]”jß  ah ]”h"]”Œ
exceptions”ah$]”h&]”uh1h´hj¯  j‚  KubhŒ:”…””}”(hj¯  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MMhj«  ubhØ)”}”(hŒ¡Some licenses can be amended with exceptions which grant certain rights
which the original license does not.  These exceptions are available
from the directory::”h]”hŒ Some licenses can be amended with exceptions which grant certain rights
which the original license does not.  These exceptions are available
from the directory:”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MOhj«  ubj  )”}”(hŒLICENSES/exceptions/”h]”hŒLICENSES/exceptions/”…””}”hjÚ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h MShj«  ubhØ)”}”(hŒin the kernel source tree.  The files in this directory contain the full
exception text and the required `Exception Metatags`_.”h]”(hŒiin the kernel source tree.  The files in this directory contain the full
exception text and the required ”…””}”(hjè  hžhhŸNh NubjF  )”}”(hŒ`Exception Metatags`_”h]”hŒException Metatags”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒException Metatags”hÀŒexception-metatags”uh1jE  hjè  ju  KubhŒ.”…””}”(hjè  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MUhj«  ubhØ)”}”(hŒ
Examples::”h]”hŒ	Examples:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MXhj«  ubj  )”}”(hŒ&LICENSES/exceptions/Linux-syscall-note”h]”hŒ&LICENSES/exceptions/Linux-syscall-note”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h MZhj«  ubhØ)”}”(hŒÈContains the Linux syscall exception as documented in the COPYING
file of the Linux kernel, which is used for UAPI header files.
e.g. /\* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note \*/::”h]”hŒÇContains the Linux syscall exception as documented in the COPYING
file of the Linux kernel, which is used for UAPI header files.
e.g. / * SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note  */:”…””}”(hj'  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M\hj«  ubj  )”}”(hŒ%LICENSES/exceptions/GCC-exception-2.0”h]”hŒ%LICENSES/exceptions/GCC-exception-2.0”…””}”hj5  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M`hj«  ubhØ)”}”(hX  Contains the GCC 'linking exception' which allows to link any binary
independent of its license against the compiled version of a file marked
with this exception. This is required for creating runnable executables
from source code which is not compatible with the GPL.”h]”hX  Contains the GCC â€˜linking exceptionâ€™ which allows to link any binary
independent of its license against the compiled version of a file marked
with this exception. This is required for creating runnable executables
from source code which is not compatible with the GPL.”…””}”(hjC  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mbhj«  ubhØ)”}”(hŒ_`Exception Metatags`:”h]”(hµ)”}”(hŒ_`Exception Metatags`”h]”hŒException Metatags”…””}”(hjU  hžhhŸNh Nubah}”(h]”j   ah ]”h"]”Œexception metatags”ah$]”h&]”uh1h´hjQ  j‚  KubhŒ:”…””}”(hjQ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mghj«  ubhØ)”}”(hŒ?The following meta tags must be available in an exception file:”h]”hŒ?The following meta tags must be available in an exception file:”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mihj«  ubj†  )”}”(hhh]”(jª  )”}”(hŒfSPDX-Exception-Identifier:

One exception identifier which can be used with SPDX license
identifiers.
”h]”(hØ)”}”(hŒSPDX-Exception-Identifier:”h]”hŒSPDX-Exception-Identifier:”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mkhj  ubhØ)”}”(hŒIOne exception identifier which can be used with SPDX license
identifiers.”h]”hŒIOne exception identifier which can be used with SPDX license
identifiers.”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mmhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj|  ubjª  )”}”(hŒdSPDX-URL:

The URL of the SPDX page which contains additional information related
to the exception.
”h]”(hØ)”}”(hŒ	SPDX-URL:”h]”hŒ	SPDX-URL:”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mphj¥  ubhØ)”}”(hŒXThe URL of the SPDX page which contains additional information related
to the exception.”h]”hŒXThe URL of the SPDX page which contains additional information related
to the exception.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mrhj¥  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj|  ubjª  )”}”(hŒhSPDX-Licenses:

A comma separated list of SPDX license identifiers for which the
exception can be used.
”h]”(hØ)”}”(hŒSPDX-Licenses:”h]”hŒSPDX-Licenses:”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MuhjË  ubhØ)”}”(hŒWA comma separated list of SPDX license identifiers for which the
exception can be used.”h]”hŒWA comma separated list of SPDX license identifiers for which the
exception can be used.”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MwhjË  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj|  ubjª  )”}”(hŒâUsage-Guidance:

Freeform text for usage advice. The text must be followed by correct
examples for the SPDX license identifiers as they should be put into
source files according to the `License identifier syntax`_ guidelines.
”h]”(hØ)”}”(hŒUsage-Guidance:”h]”hŒUsage-Guidance:”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mzhjñ  ubhØ)”}”(hŒÐFreeform text for usage advice. The text must be followed by correct
examples for the SPDX license identifiers as they should be put into
source files according to the `License identifier syntax`_ guidelines.”h]”(hŒ¨Freeform text for usage advice. The text must be followed by correct
examples for the SPDX license identifiers as they should be put into
source files according to the ”…””}”(hj	  hžhhŸNh NubjF  )”}”(hŒ`License identifier syntax`_”h]”hŒLicense identifier syntax”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLicense identifier syntax”hÀj|  uh1jE  hj	  ju  KubhŒ guidelines.”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M|hjñ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj|  ubjª  )”}”(hŒSException-Text:

All text after this tag is treated as the original exception text
”h]”(hØ)”}”(hŒException-Text:”h]”hŒException-Text:”…””}”(hj/	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M€hj+	  ubhØ)”}”(hŒAAll text after this tag is treated as the original exception text”h]”hŒAAll text after this tag is treated as the original exception text”…””}”(hj=	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M‚hj+	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj|  ubeh}”(h]”h ]”h"]”h$]”h&]”j<  j=  uh1j…  hŸh³h Mkhj«  ubhØ)”}”(hŒFile format examples::”h]”hŒFile format examples:”…””}”(hjW	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M„hj«  ubj  )”}”(hXd  SPDX-Exception-Identifier: Linux-syscall-note
SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+
Usage-Guidance:
  This exception is used together with one of the above SPDX-Licenses
  to mark user-space API (uapi) header files so they can be included
  into non GPL compliant user-space application code.
  To use this exception add it with the keyword WITH to one of the
  identifiers in the SPDX-Licenses tag:
    SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
Exception-Text:
  Full exception text”h]”hXd  SPDX-Exception-Identifier: Linux-syscall-note
SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+
Usage-Guidance:
  This exception is used together with one of the above SPDX-Licenses
  to mark user-space API (uapi) header files so they can be included
  into non GPL compliant user-space application code.
  To use this exception add it with the keyword WITH to one of the
  identifiers in the SPDX-Licenses tag:
    SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
Exception-Text:
  Full exception text”…””}”hje	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M†hj«  ubj  )”}”(hXÿ  SPDX-Exception-Identifier: GCC-exception-2.0
SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
SPDX-Licenses: GPL-2.0, GPL-2.0+
Usage-Guidance:
  The "GCC Runtime Library exception 2.0" is used together with one
  of the above SPDX-Licenses for code imported from the GCC runtime
  library.
  To use this exception add it with the keyword WITH to one of the
  identifiers in the SPDX-Licenses tag:
    SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
Exception-Text:
  Full exception text”h]”hXÿ  SPDX-Exception-Identifier: GCC-exception-2.0
SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
SPDX-Licenses: GPL-2.0, GPL-2.0+
Usage-Guidance:
  The "GCC Runtime Library exception 2.0" is used together with one
  of the above SPDX-Licenses for code imported from the GCC runtime
  library.
  To use this exception add it with the keyword WITH to one of the
  identifiers in the SPDX-Licenses tag:
    SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
Exception-Text:
  Full exception text”…””}”hjs	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h M•hj«  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j©  hj¨  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j×  jØ  jÙ  hjÚ  jÛ  j=  Kuh1j¤  hjƒ  hžhhŸh³h MMubhØ)”}”(hXf  All SPDX license identifiers and exceptions must have a corresponding file
in the LICENSES subdirectories. This is required to allow tool
verification (e.g. checkpatch.pl) and to have the licenses ready to read
and extract right from the source, which is recommended by various FOSS
organizations, e.g. the `FSFE REUSE initiative <https://reuse.software/>`_.”h]”(hX3  All SPDX license identifiers and exceptions must have a corresponding file
in the LICENSES subdirectories. This is required to allow tool
verification (e.g. checkpatch.pl) and to have the licenses ready to read
and extract right from the source, which is recommended by various FOSS
organizations, e.g. the ”…””}”(hj	  hžhhŸNh NubjF  )”}”(hŒ2`FSFE REUSE initiative <https://reuse.software/>`_”h]”hŒFSFE REUSE initiative”…””}”(hj•	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒFSFE REUSE initiative”Œrefuri”Œhttps://reuse.software/”uh1jE  hj	  ubhµ)”}”(hŒ <https://reuse.software/>”h]”h}”(h]”Œfsfe-reuse-initiative”ah ]”h"]”Œfsfe reuse initiative”ah$]”h&]”Œrefuri”j¦	  uh1h´j‚  Khj	  ubhŒ.”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M£hjƒ  hžhubeh}”(h]”jt  ah ]”h"]”Œlicense identifiers”ah$]”h&]”uh1hÂhhÄhžhhŸh³h K˜j‚  KubhÃ)”}”(hhh]”(hÈ)”}”(hŒ_`MODULE_LICENSE`”h]”hµ)”}”(hjÊ	  h]”hŒMODULE_LICENSE”…””}”(hjÌ	  hžhhŸNh Nubah}”(h]”Œmodule-license”ah ]”h"]”Œmodule_license”ah$]”h&]”uh1h´hjÈ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÅ	  hžhhŸh³h MªubhŒblock_quote”“”)”}”(hX¬  Loadable kernel modules also require a MODULE_LICENSE() tag. This tag is
neither a replacement for proper source code license information
(SPDX-License-Identifier) nor in any way relevant for expressing or
determining the exact license under which the source code of the module
is provided.

The sole purpose of this tag is to provide sufficient information
whether the module is free software or proprietary for the kernel
module loader and for user space tools.

The valid license strings for MODULE_LICENSE() are:

 ============================= =============================================
 "GPL"                         Module is licensed under GPL version 2. This
                               does not express any distinction between
                               GPL-2.0-only or GPL-2.0-or-later. The exact
                               license information can only be determined
                               via the license information in the
                               corresponding source files.

 "GPL v2"                      Same as "GPL". It exists for historic
                               reasons.

 "GPL and additional rights"   Historical variant of expressing that the
                               module source is dual licensed under a
                               GPL v2 variant and MIT license. Please do
                               not use in new code.

 "Dual MIT/GPL"                The correct way of expressing that the
                               module is dual licensed under a GPL v2
                               variant or MIT license choice.

 "Dual BSD/GPL"                The module is dual licensed under a GPL v2
                               variant or BSD license choice. The exact
                               variant of the BSD license can only be
                               determined via the license information
                               in the corresponding source files.

 "Dual MPL/GPL"                The module is dual licensed under a GPL v2
                               variant or Mozilla Public License (MPL)
                               choice. The exact variant of the MPL
                               license can only be determined via the
                               license information in the corresponding
                               source files.

 "Proprietary"                 The module is under a proprietary license.
                               "Proprietary" is to be understood only as
                               "The license is not compatible to GPLv2".
                               This string is solely for non-GPL2 compatible
                               third party modules and cannot be used for
                               modules which have their source code in the
                               kernel tree. Modules tagged that way are
                               tainting the kernel with the 'P' flag when
                               loaded and the kernel module loader refuses
                               to link such modules against symbols which
                               are exported with EXPORT_SYMBOL_GPL().
 ============================= =============================================


”h]”(hØ)”}”(hX"  Loadable kernel modules also require a MODULE_LICENSE() tag. This tag is
neither a replacement for proper source code license information
(SPDX-License-Identifier) nor in any way relevant for expressing or
determining the exact license under which the source code of the module
is provided.”h]”hX"  Loadable kernel modules also require a MODULE_LICENSE() tag. This tag is
neither a replacement for proper source code license information
(SPDX-License-Identifier) nor in any way relevant for expressing or
determining the exact license under which the source code of the module
is provided.”…””}”(hjç	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¬hjã	  ubhØ)”}”(hŒ«The sole purpose of this tag is to provide sufficient information
whether the module is free software or proprietary for the kernel
module loader and for user space tools.”h]”hŒ«The sole purpose of this tag is to provide sufficient information
whether the module is free software or proprietary for the kernel
module loader and for user space tools.”…””}”(hjõ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M²hjã	  ubhØ)”}”(hŒ3The valid license strings for MODULE_LICENSE() are:”h]”hŒ3The valid license strings for MODULE_LICENSE() are:”…””•)7      }”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¶hjã	  ubjâ	  )”}”(hX
  ============================= =============================================
"GPL"                         Module is licensed under GPL version 2. This
                              does not express any distinction between
                              GPL-2.0-only or GPL-2.0-or-later. The exact
                              license information can only be determined
                              via the license information in the
                              corresponding source files.

"GPL v2"                      Same as "GPL". It exists for historic
                              reasons.

"GPL and additional rights"   Historical variant of expressing that the
                              module source is dual licensed under a
                              GPL v2 variant and MIT license. Please do
                              not use in new code.

"Dual MIT/GPL"                The correct way of expressing that the
                              module is dual licensed under a GPL v2
                              variant or MIT license choice.

"Dual BSD/GPL"                The module is dual licensed under a GPL v2
                              variant or BSD license choice. The exact
                              variant of the BSD license can only be
                              determined via the license information
                              in the corresponding source files.

"Dual MPL/GPL"                The module is dual licensed under a GPL v2
                              variant or Mozilla Public License (MPL)
                              choice. The exact variant of the MPL
                              license can only be determined via the
                              license information in the corresponding
                              source files.

"Proprietary"                 The module is under a proprietary license.
                              "Proprietary" is to be understood only as
                              "The license is not compatible to GPLv2".
                              This string is solely for non-GPL2 compatible
                              third party modules and cannot be used for
                              modules which have their source code in the
                              kernel tree. Modules tagged that way are
                              tainting the kernel with the 'P' flag when
                              loaded and the kernel module loader refuses
                              to link such modules against symbols which
                              are exported with EXPORT_SYMBOL_GPL().
============================= =============================================


”h]”hŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j
  hj
  ubj 
  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K-uh1j
  hj
  ubhŒtbody”“”)”}”(hhh]”(hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hØ)”}”(hŒ"GPL"”h]”hŒ	â€œGPLâ€”…””}”(hjD
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¹hjA
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj<
  ubj@
  )”}”(hhh]”hØ)”}”(hŒëModule is licensed under GPL version 2. This
does not express any distinction between
GPL-2.0-only or GPL-2.0-or-later. The exact
license information can only be determined
via the license information in the
corresponding source files.”h]”hŒëModule is licensed under GPL version 2. This
does not express any distinction between
GPL-2.0-only or GPL-2.0-or-later. The exact
license information can only be determined
via the license information in the
corresponding source files.”…””}”(hj[
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¹hjX
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj<
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"GPL v2"”h]”hŒâ€œGPL v2â€”…””}”(hj{
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÀhjx
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hju
  ubj@
  )”}”(hhh]”hØ)”}”(hŒ.Same as "GPL". It exists for historic
reasons.”h]”hŒ2Same as â€œGPLâ€. It exists for historic
reasons.”…””}”(hj’
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÀhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hju
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"GPL and additional rights"”h]”hŒâ€œGPL and additional rightsâ€”…””}”(hj²
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÃhj¯
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj¬
  ubj@
  )”}”(hhh]”hØ)”}”(hŒHistorical variant of expressing that the
module source is dual licensed under a
GPL v2 variant and MIT license. Please do
not use in new code.”h]”hŒHistorical variant of expressing that the
module source is dual licensed under a
GPL v2 variant and MIT license. Please do
not use in new code.”…””}”(hjÉ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÃhjÆ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj¬
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"Dual MIT/GPL"”h]”hŒâ€œDual MIT/GPLâ€”…””}”(hjé
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÈhjæ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjã
  ubj@
  )”}”(hhh]”hØ)”}”(hŒlThe correct way of expressing that the
module is dual licensed under a GPL v2
variant or MIT license choice.”h]”hŒlThe correct way of expressing that the
module is dual licensed under a GPL v2
variant or MIT license choice.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÈhjý
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjã
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"Dual BSD/GPL"”h]”hŒâ€œDual BSD/GPLâ€”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÌhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj  ubj@
  )”}”(hhh]”hØ)”}”(hŒÄThe module is dual licensed under a GPL v2
variant or BSD license choice. The exact
variant of the BSD license can only be
determined via the license information
in the corresponding source files.”h]”hŒÄThe module is dual licensed under a GPL v2
variant or BSD license choice. The exact
variant of the BSD license can only be
determined via the license information
in the corresponding source files.”…””}”(hj7  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÌhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"Dual MPL/GPL"”h]”hŒâ€œDual MPL/GPLâ€”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÒhjT  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjQ  ubj@
  )”}”(hhh]”hØ)”}”(hŒÕThe module is dual licensed under a GPL v2
variant or Mozilla Public License (MPL)
choice. The exact variant of the MPL
license can only be determined via the
license information in the corresponding
source files.”h]”hŒÕThe module is dual licensed under a GPL v2
variant or Mozilla Public License (MPL)
choice. The exact variant of the MPL
license can only be determined via the
license information in the corresponding
source files.”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÒhjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjQ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubj;
  )”}”(hhh]”(j@
  )”}”(hhh]”hØ)”}”(hŒ"Proprietary"”h]”hŒâ€œProprietaryâ€”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÙhj‹  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjˆ  ubj@
  )”}”(hhh]”hØ)”}”(hXÕ  The module is under a proprietary license.
"Proprietary" is to be understood only as
"The license is not compatible to GPLv2".
This string is solely for non-GPL2 compatible
third party modules and cannot be used for
modules which have their source code in the
kernel tree. Modules tagged that way are
tainting the kernel with the 'P' flag when
loaded and the kernel module loader refuses
to link such modules against symbols which
are exported with EXPORT_SYMBOL_GPL().”h]”hXá  The module is under a proprietary license.
â€œProprietaryâ€ is to be understood only as
â€œThe license is not compatible to GPLv2â€.
This string is solely for non-GPL2 compatible
third party modules and cannot be used for
modules which have their source code in the
kernel tree. Modules tagged that way are
tainting the kernel with the â€˜Pâ€™ flag when
loaded and the kernel module loader refuses
to link such modules against symbols which
are exported with EXPORT_SYMBOL_GPL().”…””}”(hj¥  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MÙhj¢  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j?
  hjˆ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:
  hj7
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5
  hj
  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j
  hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j
  hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1já	  hŸh³h M¸hjã	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1já	  hŸh³h M¬hjÅ	  hžhubeh}”(h]”Œid1”ah ]”h"]”h$]”Œmodule_license”ah&]”uh1hÂhhÄhžhhŸh³h Mªj‚  Kubeh}”(h]”(Œlinux-kernel-licensing-rules”hÁeh ]”h"]”(Œlinux kernel licensing rules”Œkernel_licensing”eh$]”h&]”uh1hÂhhhžhhŸh³h KŒexpect_referenced_by_name”}”jì  h¶sŒexpect_referenced_by_id”}”hÁh¶subeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÇNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”j?
  Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”(Œlicense identifiers”]”(jd  jä  eŒ
exceptions”]”jÏ  aŒmetatags”]”(jù  jÍ  jÞ  eŒlicense identifier syntax”]”(jð  j	  eŒpreferred licenses”]”(jC  jT  eŒexception metatags”]”jð  auŒrefids”}”hÁ]”h¶asŒnameids”}”(jì  hÁjë  jè  j  j|  jÂ	  jt  jº  j·  jj  j	  j¿  jß  ja  j   j°	  j­	  jØ	  jÕ	  uŒ	nametypes”}”(jì  ˆjë  ‰j  ‰jÂ	  ‰jº  ˆjj  ˆj¿  ˆja  ˆj°	  ˆjØ	  ˆuh}”(hÁhÄjè  hÄj|  j“  jt  jƒ  j·  j­  j	  j^  jß  j³  j   jU  j­	  j§	  jÕ	  jÌ	  jà  jÅ	  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”j#  Ks…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hØ)”}”(hŒ:Enumerated list start value not ordinal-1: "2" (ordinal 2)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ2â€ (ordinal 2)”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj†  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kuh1j„  hj“  hžhhŸh³h KGubj…  )”}”(hhh]”hØ)”}”(hŒ:Enumerated list start value not ordinal-1: "3" (ordinal 3)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ3â€ (ordinal 3)”…””}”(hj¥  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj¢  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Kuh1j„  hj“  hžhhŸh³h K]ubj…  )”}”(hhh]”hØ)”}”(hŒ:Enumerated list start value not ordinal-1: "2" (ordinal 2)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ2â€ (ordinal 2)”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj½  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Kuh1j„  hjƒ  hžhhŸh³h Kíubj…  )”}”(hhh]”hØ)”}”(hŒ:Enumerated list start value not ordinal-1: "3" (ordinal 3)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ3â€ (ordinal 3)”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjØ  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Kuh1j„  hjƒ  hžhhŸh³h Mubj…  )”}”(hhh]”hØ)”}”(hŒ:Enumerated list start value not ordinal-1: "4" (ordinal 4)”h]”hŒ>Enumerated list start value not ordinal-1: â€œ4â€ (ordinal 4)”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjó  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Kuh1j„  hjƒ  hžhhŸh³h MMubj…  )”}”(hhh]”hØ)”}”(hŒ1Duplicate implicit target name: "module_license".”h]”hŒ5Duplicate implicit target name: â€œmodule_licenseâ€.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj  ubah}”(h]”h ]”h"]”h$]”h&]”jà  aŒlevel”KŒtype”jŸ  Œsource”h³Œline”Mªuh1j„  hjÅ	  hžhhŸh³h MªubeŒtransform_messages”]”(j…  )”}”(hhh]”hØ)”}”(hhh]”hŒ6Hyperlink target "kernel-licensing" is not referenced.”…””}”hj.  sbah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj+  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Kuh1j„  ubj…  )”}”(hhh]”hØ)”}”(hhh]”hŒ4Hyperlink target "module_license" is not referenced.”…””}”hjH  sbah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjE  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jŸ  Œsource”h³Œline”Mªuh1j„  ubeŒtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.