diff mbox series

docs: kbuild: Fix a typo in the file Kconfig.recursion-issue-02

Message ID 20210314043044.15926-1-unixbhaskar@gmail.com (mailing list archive)
State New
Headers show
Series docs: kbuild: Fix a typo in the file Kconfig.recursion-issue-02 | expand

Commit Message

Bhaskar Chowdhury March 14, 2021, 4:30 a.m. UTC
s/sematics/semantics/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
 Documentation/kbuild/Kconfig.recursion-issue-02 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--
2.26.2

Comments

Randy Dunlap March 14, 2021, 6:15 a.m. UTC | #1
On 3/13/21 8:30 PM, Bhaskar Chowdhury wrote:
> 
> s/sematics/semantics/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  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
> --
Masahiro Yamada March 15, 2021, 4:24 p.m. UTC | #2
On Sun, Mar 14, 2021 at 1:33 PM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>
>
> s/sematics/semantics/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---

Applied to linux-kbuild. Thanks.


>  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
>
diff mbox series

Patch

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