From: David Hildenbrand <david@redhat.com>
To: Jeongtae Park <jtp.park@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc: fix a typo in comment
Date: Thu, 4 Jun 2020 16:38:32 +0200 [thread overview]
Message-ID: <b0e5110b-3eba-e212-5299-d68585c9730c@redhat.com> (raw)
In-Reply-To: <20200604185239.20765-1-jtp.park@samsung.com>
On 04.06.20 20:52, Jeongtae Park wrote:
> There is a typo in comment, fix it.
> "nother" -> "another"
>
> Signed-off-by: Jeongtae Park <jtp.park@samsung.com>
> Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
> Cc: Christoph Hellwig <hch@lst.de>
> ---
> mm/vmalloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 1e94497b7388..3091c2ca60df 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2317,7 +2317,7 @@ static inline void __vfree_deferred(const void *addr)
> * Use raw_cpu_ptr() because this can be called from preemptible
> * context. Preemption is absolutely fine here, because the llist_add()
> * implementation is lockless, so it works even if we are adding to
> - * nother cpu's list. schedule_work() should be fine with this too.
> + * another cpu's list. schedule_work() should be fine with this too.
> */
> struct vfree_deferred *p = raw_cpu_ptr(&vfree_deferred);
>
>
fwiw
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-06-04 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200604095241epcas2p3bef5ec0a913244bcfd8e7a84827bbf77@epcas2p3.samsung.com>
2020-06-04 18:52 ` Jeongtae Park
2020-06-04 14:38 ` David Hildenbrand [this message]
2020-04-04 6:01 [PATCH] mm/vmalloc: Fix " Qiujun Huang
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=b0e5110b-3eba-e212-5299-d68585c9730c@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=hch@lst.de \
--cc=jtp.park@samsung.com \
--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
all inboxes | Powered by JetHome®