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

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


-- 
~Randy

Reply via email to