linux-kernel - Re: [PATCH] docs: kbuild: Fix a typo in the file Kconfig.recursion-issue-02

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]

Message-ID: <ad52ed1d-92b1-8320-ff70-bc9d1a9b8991@infradead.org>
Date:   Sat, 13 Mar 2021 22:15:00 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, masahiroy@...nel.org,
        michal.lkml@...kovi.net, corbet@....net,
        linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: kbuild: Fix a typo in the file
 Kconfig.recursion-issue-02

On 3/13/21 8:30 PM, Bhaskar Chowdhury wrote:
> 
> s/sematics/semantics/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.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
> --


-- 
~Randy