linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc.c: fix a comment
Date: Sun, 27 Feb 2022 08:29:36 -0800	[thread overview]
Message-ID: <572369c5-85e4-75af-85f4-d150c25e75fd@infradead.org> (raw)
In-Reply-To: <20220227084544.4681-1-caoyixuan2019@email.szu.edu.cn>



On 2/27/22 00:45, Yixuan Cao wrote:
> Dear Sir/Madam,
> 
> The sentence
> "but the mempolcy want to alloc memory by interleaving"
> should be rephrased with
> "but the mempolicy wants to alloc memory by interleaving"
> where "mempolicy" is a struct name.
> 
> Thanks and best regards,
> Yixuan Cao
> 
> Signed-off-by: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
> ---
>  mm/vmalloc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index b454cf1a261f..89d48d8eb20c 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2905,7 +2905,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
>  			/* memory allocation should consider mempolicy, we can't
>  			 * wrongly use nearest node when nid == NUMA_NO_NODE,
>  			 * otherwise memory may be allocated in only one node,
> -			 * but mempolcy want to alloc memory by interleaving.
> +			 * but mempolicy want to alloc memory by interleaving.

s/want/wants/
as in your commentary above.

>  			 */
>  			if (IS_ENABLED(CONFIG_NUMA) && nid == NUMA_NO_NODE)
>  				nr = alloc_pages_bulk_array_mempolicy(bulk_gfp,

thanks.
-- 
~Randy


      reply	other threads:[~2022-02-27 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  8:45 Yixuan Cao
2022-02-27 16:29 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=572369c5-85e4-75af-85f4-d150c25e75fd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=caoyixuan2019@email.szu.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox