From: Mike Rapoport <rppt@kernel.org>
To: Chen Tao <chentao3@hotmail.com>
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix some comments formatting
Date: Mon, 21 Sep 2020 15:20:33 +0300 [thread overview]
Message-ID: <20200921122033.GS2142832@kernel.org> (raw)
In-Reply-To: <HK0PR02MB3634AB83890BA58E709FC78186200@HK0PR02MB3634.apcprd02.prod.outlook.com>
On Tue, Sep 15, 2020 at 09:39:56AM -0700, Chen Tao wrote:
> Correct one function name "get_partials" with "get_partial".
> Update the old struct name of list3 with kmem_cache_node.
>
> Signed-off-by: Chen Tao <chentao3@hotmail.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> mm/slab.c | 2 +-
> mm/slub.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index 3160dff6fd76..0a13cce5d016 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -1062,7 +1062,7 @@ int slab_prepare_cpu(unsigned int cpu)
> * Even if all the cpus of a node are down, we don't free the
> * kmem_cache_node of any cache. This to avoid a race between cpu_down, and
> * a kmalloc allocation from another cpu for memory from the node of
> - * the cpu going down. The list3 structure is usually allocated from
> + * the cpu going down. The kmem_cache_node structure is usually allocated from
> * kmem_cache_create() and gets destroyed at kmem_cache_destroy().
> */
> int slab_dead_cpu(unsigned int cpu)
> diff --git a/mm/slub.c b/mm/slub.c
> index d4177aecedf6..1faa9ada3f51 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -1960,7 +1960,7 @@ static void *get_partial_node(struct kmem_cache *s, struct kmem_cache_node *n,
> /*
> * Racy check. If we mistakenly see no partial slabs then we
> * just allocate an empty slab. If we mistakenly try to get a
> - * partial slab and there is none available then get_partials()
> + * partial slab and there is none available then get_partial()
> * will return NULL.
> */
> if (!n || !n->nr_partial)
> --
> 2.17.1
>
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2020-09-21 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 16:39 [PATCH] mm: fix some comments formatting Chen Tao
2020-09-21 12:20 ` Mike Rapoport [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=20200921122033.GS2142832@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chentao3@hotmail.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.