* [merged] mm-vmalloc-fix-a-typo-in-comment.patch removed from -mm tree
@ 2020-06-05 20:17 akpm
0 siblings, 0 replies; 2+ messages in thread
From: akpm @ 2020-06-05 20:17 UTC (permalink / raw)
To: aryabinin, david, hch, jtp.park, mm-commits
The patch titled
Subject: mm/vmalloc: fix a typo in comment
has been removed from the -mm tree. Its filename was
mm-vmalloc-fix-a-typo-in-comment.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Jeongtae Park <jtp.park@samsung.com>
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 <jtp.park@samsung.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [merged] mm-vmalloc-fix-a-typo-in-comment.patch removed from -mm tree
@ 2020-04-08 1:56 akpm
0 siblings, 0 replies; 2+ messages in thread
From: akpm @ 2020-04-08 1:56 UTC (permalink / raw)
To: akpm, hqjagain, mm-commits
The patch titled
Subject: mm/vmalloc: fix a typo in comment
has been removed from the -mm tree. Its filename was
mm-vmalloc-fix-a-typo-in-comment.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Qiujun Huang <hqjagain@gmail.com>
Subject: mm/vmalloc: fix a typo in comment
There is a typo in comment, fix it.
"exeeds" -> "exceeds"
Link: http://lkml.kernel.org/r/20200404060136.10838-1-hqjagain@gmail.com
Signed-off-by: Qiujun Huang <hqjagain@gmail.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
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
@@ -3368,7 +3368,7 @@ retry:
goto overflow;
/*
- * If required width exeeds current VA block, move
+ * If required width exceeds current VA block, move
* base downwards and then recheck.
*/
if (base + end > va->va_end) {
_
Patches currently in -mm which might be from hqjagain@gmail.com are
mm-slab_common-fix-a-typo-in-comment-eariler-earlier.patch
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-06-05 20:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-05 20:17 [merged] mm-vmalloc-fix-a-typo-in-comment.patch removed from -mm tree akpm
-- strict thread matches above, loose matches on Subject: below --
2020-04-08 1:56 akpm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).