The patch titled
Subject: mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes
has been removed from the -mm tree. Its filename was
mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes.patch
This patch was dropped because it was folded into mm-vmalloc-fix-vmalloc-users-tracking-properly.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#4:
1f5307b1e094 ("mm, vmalloc: properly track vmalloc users") has pulled
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#12:
>> arch/m68k/include/asm/mcf_pgtable.h:339:43: error: 'init_mm' undeclared (first use in this function)
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#36:
This patch reverts 1f5307b1e094 and reimplements the original fix in a
WARNING: line over 80 characters
#71: FILE: include/linux/vmalloc.h:85:
+static inline void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void* caller)
ERROR: "foo* bar" should be "foo *bar"
#71: FILE: include/linux/vmalloc.h:85:
+static inline void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void* caller)
ERROR: "foo* bar" should be "foo *bar"
#92: FILE: include/linux/vmalloc.h:96:
+ int node, gfp_t flags, void* caller);
WARNING: line over 80 characters
#143: FILE: mm/vmalloc.c:1820:
+void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void *caller)
total: 4 errors, 3 warnings, 80 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
./patches/mm-vmalloc-fix-vmalloc-users-tracking-properly.patch has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: Michal Hocko <mhocko@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/vmalloc.h | 5 +++--
mm/vmalloc.c | 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff -puN include/linux/vmalloc.h~mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes include/linux/vmalloc.h
--- a/include/linux/vmalloc.h~mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes
+++ a/include/linux/vmalloc.h
@@ -82,13 +82,14 @@ extern void *__vmalloc_node_range(unsign
const void *caller);
#ifndef CONFIG_MMU
extern void *__vmalloc_node_flags(unsigned long size, int node, gfp_t flags);
-static inline void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void* caller)
+static inline void *__vmalloc_node_flags_caller(unsigned long size, int node,
+ gfp_t flags, void *caller)
{
return __vmalloc_node_flags(size, node, flags);
}
#else
extern void *__vmalloc_node_flags_caller(unsigned long size,
- int node, gfp_t flags, void* caller);
+ int node, gfp_t flags, void *caller);
#endif
extern void vfree(const void *addr);
diff -puN mm/vmalloc.c~mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes mm/vmalloc.c
--- a/mm/vmalloc.c~mm-vmalloc-fix-vmalloc-users-tracking-properly-checkpatch-fixes
+++ a/mm/vmalloc.c
@@ -1817,7 +1817,8 @@ static inline void *__vmalloc_node_flags
}
-void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void *caller)
+void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags,
+ void *caller)
{
return __vmalloc_node(size, 1, flags, PAGE_KERNEL, node, caller);
}
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
mm-vmalloc-fix-vmalloc-users-tracking-properly.patch
tigran-has-moved.patch
mm-vmscan-scan-until-it-founds-eligible-pages-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
