linux-kernel - [PATCH] TASK :Linux Kernel Bug Fixing: Fixing Warning/Spelling checks on the rst file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAG+54Db5eJVogCLKr3y5W02-Ksn7ChTpzz+UJaeoXJxA_V-QtQ@mail.gmail.com>
Date: Tue, 13 May 2025 19:18:47 +0530
From: rujra <braker.noob.kernel@...il.com>
To: skhan@...uxfoundation.org, corbet@....net
Cc: workflows@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: [PATCH] TASK :Linux Kernel Bug Fixing: Fixing Warning/Spelling checks
 on the rst file

TASK : Documentation Task
removed warnings and added "SPDX-License-Identifier: GPL-2.0"
in starting of the file , also instead of using re-use , have used
reuse.

Signed-off-by: Rujra Bhatt <braker.noob.kernel@...il.com>
<rujrabhatt3@...il.com>
---
 Documentation/process/adding-syscalls.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/process/adding-syscalls.rst
b/Documentation/process/adding-syscalls.rst
index 906c47f1a9e5..17652610450d 100644
--- a/Documentation/process/adding-syscalls.rst
+++ b/Documentation/process/adding-syscalls.rst
@@ -1,4 +1,4 @@
-
+.. SPDX-License-Identifier: GPL-2.0
 .. _addsyscalls:

 Adding a New System Call
@@ -117,7 +117,7 @@ then the flags argument should include a value
that is equivalent to setting
 the timing window between ``xyzzy()`` and calling
 ``fcntl(fd, F_SETFD, FD_CLOEXEC)``, where an unexpected ``fork()`` and
 ``execve()`` in another thread could leak a descriptor to
-the exec'ed program. (However, resist the temptation to re-use the actual value
+the exec'ed program. (However, resist the temptation to reuse the actual value
 of the ``O_CLOEXEC`` constant, as it is architecture-specific and is part of a
 numbering space of ``O_*`` flags that is fairly full.)

@@ -378,7 +378,7 @@ the compatibility wrapper::
     ...
     555   x32      xyzzy     __x32_compat_sys_xyzzy

-If no pointers are involved, then it is preferable to re-use the 64-bit system
+If no pointers are involved, then it is preferable to reuse the 64-bit system
 call for the x32 ABI (and consequently the entry in
 arch/x86/entry/syscalls/syscall_64.tbl is unchanged).

--
2.43.0