[<prev] [next>] [day] [month] [year] [list]
Message-ID: <3a15563b-de6c-7808-3c3c-f2ff12dc46de@nvidia.com>
Date: Wed, 15 Apr 2020 11:32:12 -0700
From: Ralph Campbell <rcampbell@...dia.com>
To: Ethon Paul <ethp@...com>, <akpm@...ux-foundation.org>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/memblock: Fix a typo in comment "implict"->"implicit"
On 4/11/20 12:07 AM, Ethon Paul wrote:
> There is a typo in commet, fix it.
>
> Signed-off-by: Ethon Paul <ethp@...com>
Reviewed-by: Ralph Campbell <rcampbell@...dia.com>
> ---
> mm/memblock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 4d06bbaded0f..4cae23d2373a 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -78,7 +78,7 @@
> * * memblock_alloc*() - these functions return the **virtual** address
> * of the allocated memory.
> *
> - * Note, that both API variants use implict assumptions about allowed
> + * Note, that both API variants use implicit assumptions about allowed
> * memory ranges and the fallback methods. Consult the documentation
> * of memblock_alloc_internal() and memblock_alloc_range_nid()
> * functions for more elaborate description.
>
Powered by blists - more mailing lists