xiaomi-sm8450/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: fix typos in license-rules.rst

Browse Source 
The patches fixes some typos in process/license-rules.rst

Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Federico Vaga
2019-02-20 23:46:09 +01:00
committed by Jonathan Corbet
parent f07fb1088f
commit 61ab9fecaf
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/process/license-rules.rst
View File

@@ -62,7 +62,7 @@ License identifier syntax
The SPDX license identifier in kernel files shall be added at the first 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 possible line in a file which can contain a comment. For the majority
or files this is the first line, except for scripts which require the 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 '#!PATH_TO_INTERPRETER' in the first line. For those scripts the SPDX
identifier goes into the second line. identifier goes into the second line.
@@ -368,7 +368,7 @@ kernel, can be broken down into:
All SPDX license identifiers and exceptions must have a corresponding file All SPDX license identifiers and exceptions must have a corresponding file
in the LICENSE subdirectories. This is required to allow tool in the LICENSES subdirectories. This is required to allow tool
verification (e.g. checkpatch.pl) and to have the licenses ready to read 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 and extract right from the source, which is recommended by various FOSS
organizations, e.g. the `FSFE REUSE initiative <https://reuse.software/>`_. organizations, e.g. the `FSFE REUSE initiative <https://reuse.software/>`_.