The patch titled
Subject: mm/gup.c: fix coding style issues.
has been added to the -mm tree. Its filename is
mm-gupc-fixed-coding-style-issues.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-gupc-fixed-coding-style-issues.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-gupc-fixed-coding-style-issues.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/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Mario Leinweber <marioleinweber@xxxxxx>
Subject: mm/gup.c: fix coding style issues.
- Fixed style error: 8 spaces -> 1 tab.
- Fixed style warning: Corrected misleading indentation.
Link: http://lkml.kernel.org/r/20180302210254.31888-1-marioleinweber@xxxxxx
Signed-off-by: Mario Leinweber <marioleinweber@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/gup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN mm/gup.c~mm-gupc-fixed-coding-style-issues mm/gup.c
--- a/mm/gup.c~mm-gupc-fixed-coding-style-issues
+++ a/mm/gup.c
@@ -531,7 +531,7 @@ static int faultin_page(struct task_stru
* reCOWed by userspace write).
*/
if ((ret & VM_FAULT_WRITE) && !(vma->vm_flags & VM_WRITE))
- *flags |= FOLL_COW;
+ *flags |= FOLL_COW;
return 0;
}
@@ -1638,7 +1638,7 @@ static int gup_pmd_range(pud_t pud, unsi
PMD_SHIFT, next, write, pages, nr))
return 0;
} else if (!gup_pte_range(pmd, addr, next, write, pages, nr))
- return 0;
+ return 0;
} while (pmdp++, addr = next, addr != end);
return 1;
_
Patches currently in -mm which might be from marioleinweber@xxxxxx are
mm-gupc-fixed-coding-style-issues.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
