On Mon, 29 Oct 2018 05:15:16 PDT (-0700), david.abdurachma...@gmail.com wrote:
Depends on:
http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
Signed-off-by: David Abdurachmanov
---
On Mon, 29 Oct 2018 05:15:16 PDT (-0700), david.abdurachma...@gmail.com wrote:
Depends on:
http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
Signed-off-by: David Abdurachmanov
---
On Mon, Oct 29, 2018 at 1:15 PM David Abdurachmanov
wrote:
>
> Depends on:
> http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
>
> Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
>
I looked this morning into Documentation/trace/ftrace-design.rst again.
On Mon, Oct 29, 2018 at 1:15 PM David Abdurachmanov
wrote:
>
> Depends on:
> http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
>
> Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
>
I looked this morning into Documentation/trace/ftrace-design.rst again.
Depends on:
http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
Signed-off-by: David Abdurachmanov
---
arch/riscv/kernel/ptrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Depends on:
http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
Signed-off-by: David Abdurachmanov
---
arch/riscv/kernel/ptrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
6 matches
Mail list logo