linux-kernel - [PATCH 14/23] trace: ftrace-uses.rst: Fix a typo

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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 29 Mar 2021 10:42:50 +0530
From:   Bhaskar Chowdhury <unixbhaskar@...il.com>
To:     corbet@....net, linux-doc@...r.kernel.org
Cc:     Bhaskar Chowdhury <unixbhaskar@...il.com>, rdunlap@...radead.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH 14/23] trace: ftrace-uses.rst: Fix a typo

s/preemptable/preemptible/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
 Documentation/trace/ftrace-uses.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst
index f7d98ae5b885..2903a58f5ac2 100644
--- a/Documentation/trace/ftrace-uses.rst
+++ b/Documentation/trace/ftrace-uses.rst
@@ -193,7 +193,7 @@ FTRACE_OPS_FL_RECURSION
 	Not, if this flag is set, then the callback will always be called
 	with preemption disabled. If it is not set, then it is possible
 	(but not guaranteed) that the callback will be called in
-	preemptable context.
+	preemptible context.

 FTRACE_OPS_FL_IPMODIFY
 	Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack"
--
2.26.3