lkml.org 
[lkml]   [2019]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] mm/memblock: fix typo in memblock doc
On Wed, Sep 11, 2019 at 11:08:56AM +0800, Cao jin wrote:
> elaboarte -> elaborate
> architecure -> architecture
> compltes -> completes
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> mm/memblock.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 7d4f61ae666a..0d0f92003d18 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -83,16 +83,16 @@
> * Note, that both API variants use implict assumptions about allowed
> * memory ranges and the fallback methods. Consult the documentation
> * of :c:func:`memblock_alloc_internal` and
> - * :c:func:`memblock_alloc_range_nid` functions for more elaboarte
> + * :c:func:`memblock_alloc_range_nid` functions for more elaborate

While on it, could you please replace the
:c:func:`memblock_alloc_range_nid` construct with
memblock_alloc_range_nid()?

And that would be really great to see all the :c:func:`foo` changed to
foo().

> * description.
> *
> * As the system boot progresses, the architecture specific
> * :c:func:`mem_init` function frees all the memory to the buddy page
> * allocator.
> *
> - * Unless an architecure enables %CONFIG_ARCH_KEEP_MEMBLOCK, the
> + * Unless an architecture enables %CONFIG_ARCH_KEEP_MEMBLOCK, the
> * memblock data structures will be discarded after the system
> - * initialization compltes.
> + * initialization completes.
> */
>
> #ifndef CONFIG_NEED_MULTIPLE_NODES
> --
> 2.21.0
>
>
>

--
Sincerely yours,
Mike.

\
 
 \ /
  Last update: 2019-09-11 16:44    [W:0.052 / U:0.020 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site