The patch titled
Subject: powerpc/kprobes: fixup for kprobes declarations moving
has been added to the -mm tree. Its filename is
kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2.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: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Subject: powerpc/kprobes: fixup for kprobes declarations moving
Link: http://lkml.kernel.org/r/20170214165933.13ebd4f4@xxxxxxxxxxxxxxxx
Signed-off-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Cc: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/powerpc/lib/code-patching.c | 1 +
1 file changed, 1 insertion(+)
diff -puN arch/powerpc/lib/code-patching.c~kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2 arch/powerpc/lib/code-patching.c
--- a/arch/powerpc/lib/code-patching.c~kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2
+++ a/arch/powerpc/lib/code-patching.c
@@ -14,6 +14,7 @@
#include <asm/page.h>
#include <asm/code-patching.h>
#include <linux/uaccess.h>
+#include <linux/kprobes.h>
int patch_instruction(unsigned int *addr, unsigned int instr)
_
Patches currently in -mm which might be from sfr@xxxxxxxxxxxxxxxx are
kprobes-move-kprobe-declarations-to-asm-generic-kprobesh-fix-2.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
