[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210314043044.15926-1-unixbhaskar@gmail.com>
Date: Sun, 14 Mar 2021 10:00:44 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: masahiroy@...nel.org, michal.lkml@...kovi.net, corbet@....net,
linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH] docs: kbuild: Fix a typo in the file Kconfig.recursion-issue-02
s/sematics/semantics/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
Documentation/kbuild/Kconfig.recursion-issue-02 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/kbuild/Kconfig.recursion-issue-02 b/Documentation/kbuild/Kconfig.recursion-issue-02
index df245fd7670d..0034eb494d11 100644
--- a/Documentation/kbuild/Kconfig.recursion-issue-02
+++ b/Documentation/kbuild/Kconfig.recursion-issue-02
@@ -6,7 +6,7 @@
# make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
#
# The recursive limitations with Kconfig has some non intuitive implications on
-# kconfig sematics which are documented here. One known practical implication
+# kconfig semantics which are documented here. One known practical implication
# of the recursive limitation is that drivers cannot negate features from other
# drivers if they share a common core requirement and use disjoint semantics to
# annotate those requirements, ie, some drivers use "depends on" while others
--
2.26.2
Powered by blists - more mailing lists