The patch titled
Subject: kernel/kcmp.c: drop branch leftover typo
has been added to the -mm tree. Its filename is
kcmp-drop-branch-leftover-typo.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/kcmp-drop-branch-leftover-typo.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/kcmp-drop-branch-leftover-typo.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: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
Subject: kernel/kcmp.c: drop branch leftover typo
The else branch been left over and escaped the source code refresh. Not a
problem but better clean it up.
Fixes: 0791e3644e5e ("kcmp: add KCMP_EPOLL_TFD mode to compare epoll target files")
Link: http://lkml.kernel.org/r/20170917165838.GA1887@xxxxxxxxxx
Reported-by: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
Signed-off-by: Cyrill Gorcunov <gorcunov@xxxxxxxxxx>
Acked-by: Andrei Vagin <avagin@xxxxxxxxxxxxx>
Cc: Pavel Emelyanov <xemul@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/kcmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/kcmp.c~kcmp-drop-branch-leftover-typo kernel/kcmp.c
--- a/kernel/kcmp.c~kcmp-drop-branch-leftover-typo
+++ a/kernel/kcmp.c
@@ -131,7 +131,7 @@ static int kcmp_epoll_target(struct task
if (filp_epoll) {
filp_tgt = get_epoll_tfile_raw_ptr(filp_epoll, slot.tfd, slot.toff);
fput(filp_epoll);
- } else
+ }
if (IS_ERR(filp_tgt))
return PTR_ERR(filp_tgt);
_
Patches currently in -mm which might be from gorcunov@xxxxxxxxx are
kcmp-drop-branch-leftover-typo.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
