From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: palmer@sifive.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Cc: David Abdurachmanov <david.abdurachmanov@gmail.com>
Subject: [PATCH 0/2] Fix next-audit branch
Date: Mon, 10 Dec 2018 21:43:53 +0100 [thread overview]
Message-ID: <20181210204355.3483-1-david.abdurachmanov@gmail.com> (raw)
Intel kbuild test robot reported on Dec 8th, 2018 that next-audit is
broken. This was with riscv-allmodconfig config.
There were two issues found:
- We don't generate functions needed for trace events;
- We are missing NR_syscalls macro used by kernel/trace.
David Abdurachmanov (2):
riscv: define NR_syscalls in unistd.h
riscv: define CREATE_TRACE_POINTS in ptrace.c
arch/riscv/include/asm/unistd.h | 2 ++
arch/riscv/kernel/ptrace.c | 2 ++
2 files changed, 4 insertions(+)
--
2.19.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-12-10 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 20:43 David Abdurachmanov [this message]
2018-12-10 20:43 ` [PATCH 1/2] riscv: define NR_syscalls in unistd.h David Abdurachmanov
2018-12-14 1:57 ` Olof Johansson
2018-12-10 20:43 ` [PATCH 2/2] riscv: define CREATE_TRACE_POINTS in ptrace.c David Abdurachmanov
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=20181210204355.3483-1-david.abdurachmanov@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).