The patch titled
Subject: fs/userfaultfd.c: drop dead code
has been added to the -mm tree. Its filename is
userfaultfd-drop-dead-code.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/userfaultfd-drop-dead-code.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/userfaultfd-drop-dead-code.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: "Mike Rapoport" <rppt@xxxxxxxxxxxxxxxxxx>
Subject: fs/userfaultfd.c: drop dead code
Calculation of start end end in __wake_userfault function are not used and
can be removed.
Link: http://lkml.kernel.org/r/1494930917-3134-1-git-send-email-rppt@xxxxxxxxxxxxxxxxxx
Signed-off-by: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
Cc: Andrea Arcangeli <aarcange@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/userfaultfd.c | 5 -----
1 file changed, 5 deletions(-)
diff -puN fs/userfaultfd.c~userfaultfd-drop-dead-code fs/userfaultfd.c
--- a/fs/userfaultfd.c~userfaultfd-drop-dead-code
+++ a/fs/userfaultfd.c
@@ -1101,11 +1101,6 @@ static ssize_t userfaultfd_read(struct f
static void __wake_userfault(struct userfaultfd_ctx *ctx,
struct userfaultfd_wake_range *range)
{
- unsigned long start, end;
-
- start = range->start;
- end = range->start + range->len;
-
spin_lock(&ctx->fault_pending_wqh.lock);
/* wake all in the range and autoremove */
if (waitqueue_active(&ctx->fault_pending_wqh))
_
Patches currently in -mm which might be from rppt@xxxxxxxxxxxxxxxxxx are
exit-dont-include-unused-userfaultfd_kh.patch
userfaultfd-drop-dead-code.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
