From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: + mm-vmalloc-fix-a-typo-in-comment.patch added to -mm tree Date: Thu, 04 Jun 2020 11:03:37 -0700 Message-ID: <20200604180337.lQ_-QH1oI%akpm@linux-foundation.org> References: <20200603155549.e041363450869eaae4c7f05b@linux-foundation.org> Reply-To: linux-kernel@vger.kernel.org Return-path: Received: from mail.kernel.org ([198.145.29.99]:38268 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730055AbgFDSDi (ORCPT ); Thu, 4 Jun 2020 14:03:38 -0400 In-Reply-To: <20200603155549.e041363450869eaae4c7f05b@linux-foundation.org> Sender: mm-commits-owner@vger.kernel.org List-Id: mm-commits@vger.kernel.org To: aryabinin@virtuozzo.com, david@redhat.com, hch@lst.de, jtp.park@samsung.com, mm-commits@vger.kernel.org The patch titled Subject: mm/vmalloc: fix a typo in comment has been added to the -mm tree. Its filename is mm-vmalloc-fix-a-typo-in-comment.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/mm-vmalloc-fix-a-typo-in-comment.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/mm-vmalloc-fix-a-typo-in-comment.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Jeongtae Park Subject: mm/vmalloc: fix a typo in comment There is a typo in comment, fix it. "nother" -> "another" Link: http://lkml.kernel.org/r/20200604185239.20765-1-jtp.park@samsung.com Signed-off-by: Jeongtae Park Reviewed-by: David Hildenbrand Cc: Andrey Ryabinin Cc: Christoph Hellwig Signed-off-by: Andrew Morton --- mm/vmalloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/mm/vmalloc.c~mm-vmalloc-fix-a-typo-in-comment +++ a/mm/vmalloc.c @@ -2317,7 +2317,7 @@ static inline void __vfree_deferred(cons * 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); _ Patches currently in -mm which might be from jtp.park@samsung.com are mm-vmalloc-fix-a-typo-in-comment.patch