The patch titled
Subject: mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes
has been added to the -mm tree. Its filename is
mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes.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: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes
WARNING: line over 80 characters
#27: FILE: mm/z3fold.c:199:
+ (gfp & ~(__GFP_HIGHMEM
WARNING: line over 80 characters
#28: FILE: mm/z3fold.c:200:
+ | __GFP_MOVABLE)));
total: 0 errors, 2 warnings, 17 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-z3foldc-allow-__gfp_highmem-in-z3fold_alloc.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: Henry Burns <henryburns@xxxxxxxxxx>
Cc: Shakeel Butt <shakeelb@xxxxxxxxxx>
Cc: Vitaly Wool <vitalywool@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/z3fold.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--- a/mm/z3fold.c~mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes
+++ a/mm/z3fold.c
@@ -195,9 +195,10 @@ static void compact_page_work(struct wor
static inline struct z3fold_buddy_slots *alloc_slots(struct z3fold_pool *pool,
gfp_t gfp)
{
- struct z3fold_buddy_slots *slots = kmem_cache_alloc(pool->c_handle,
- (gfp & ~(__GFP_HIGHMEM
- | __GFP_MOVABLE)));
+ struct z3fold_buddy_slots *slots;
+
+ slots = kmem_cache_alloc(pool->c_handle,
+ (gfp & ~(__GFP_HIGHMEM | __GFP_MOVABLE)));
if (slots) {
memset(slots->slot, 0, sizeof(slots->slot));
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
mm-z3foldc-allow-__gfp_highmem-in-z3fold_alloc-checkpatch-fixes.patch
ocfs2-clear-zero-in-unaligned-direct-io-checkpatch-fixes.patch
mm.patch
mm-vmscanc-add-checks-for-incorrect-handling-of-current-reclaim_state.patch
mm-oom_killer-add-task-uid-to-info-message-on-an-oom-kill-fix.patch
mm-thp-make-transhuge_vma_suitable-available-for-anonymous-thp-fix.patch
vmcore-add-a-kernel-parameter-novmcoredd-fix.patch
vmcore-add-a-kernel-parameter-novmcoredd-fix-fix.patch
rbtree-avoid-generating-code-twice-for-the-cached-versions-checkpatch-fixes.patch
coda-add-hinting-support-for-partial-file-caching-fix.patch
selftests-ptrace-add-a-test-case-for-ptrace_get_syscall_info-checkpatch-fixes.patch
resource-fix-locking-in-find_next_iomem_res-fix.patch
linux-next-git-rejects.patch
diff-sucks.patch
mm-section-numbers-use-the-type-unsigned-long-fix.patch
mm-sparsemem-cleanup-section-number-data-types-fix.patch
proc-sysctl-add-shared-variables-for-range-check-fix-2-fix.patch
proc-sysctl-add-shared-variables-for-range-check-fix-4.patch
drivers-tty-serial-sh-scic-suppress-warning.patch
kernel-forkc-export-kernel_thread-to-modules.patch
