From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: enable syscalls tracepoints
Date: Mon, 10 Dec 2018 21:48:36 +0100 [thread overview]
Message-ID: <CAEn-LTqP70BXjVGosw1KFTP1gSaTdji3174Hc3skZA2chdJXgA@mail.gmail.com> (raw)
In-Reply-To: <mhng-49f84968-18a7-4acb-b41a-f056d1ee7034@palmer-si-x1c4>
On Fri, Dec 7, 2018 at 9:32 PM Palmer Dabbelt <palmer@sifive.com> wrote:
>
> On Thu, 06 Dec 2018 07:26:33 PST (-0800), david.abdurachmanov@gmail.com wrote:
> > Depends on audit patch:
> > http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
> >
> > audit patch is already merged into linux-next.
> >
> > This simply fixes compilation error in do_syscall_trace_exit() and
> > enables syscalls tracepoints.
> >
> > David Abdurachmanov (2):
> > riscv: fix trace_sys_exit hook
> > riscv: add HAVE_SYSCALL_TRACEPOINTS to Kconfig
> >
> > arch/riscv/Kconfig | 1 +
> > arch/riscv/kernel/ptrace.c | 2 +-
> > 2 files changed, 2 insertions(+), 1 deletion(-)
>
> I've attempted to add this on top of next-audit, which I've merged into
> for-next. Let me know if something went wrong.
Two things:
- The order of commits are wrong. Right now the commits are in
reverse order, i.e. audit patches are on top.
- Intel kbuild test bot found compilation errors with riscv-allmodconfig
config. I fixed those and posted two patches:
http://lists.infradead.org/pipermail/linux-riscv/2018-December/002508.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2018-12-10 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:26 [PATCH 0/2] riscv: enable syscalls tracepoints David Abdurachmanov
2018-12-06 15:26 ` [PATCH 1/2] riscv: fix trace_sys_exit hook David Abdurachmanov
2018-12-06 15:26 ` [PATCH 2/2] riscv: add HAVE_SYSCALL_TRACEPOINTS to Kconfig David Abdurachmanov
2018-12-07 20:32 ` [PATCH 0/2] riscv: enable syscalls tracepoints Palmer Dabbelt
2018-12-10 20:48 ` David Abdurachmanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEn-LTqP70BXjVGosw1KFTP1gSaTdji3174Hc3skZA2chdJXgA@mail.gmail.com \
--to=david.abdurachmanov@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).