From: kbuild test robot <lkp@intel.com>
To: Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca>
Cc: kbuild-all@01.org, rostedt@goodmis.org, mingo@redhat.com,
peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: instrument security and console initcall
Date: Sat, 24 Mar 2018 22:11:19 +0800 [thread overview]
Message-ID: <201803242225.CpaSAi5v%fengguang.wu@intel.com> (raw)
In-Reply-To: <1521765208.19745.2.camel@polymtl.ca>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi Abderrahmane,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc6 next-20180323]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Abderrahmane-Benbachir/trace-instrument-security-and-console-initcall/20180324-215004
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> kernel/printk/printk.c:55:10: fatal error: trace/events/boot.h: No such file or directory
#include <trace/events/boot.h>
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +55 kernel/printk/printk.c
54
> 55 #include <trace/events/boot.h>
56 #define CREATE_TRACE_POINTS
57 #include <trace/events/printk.h>
58
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6733 bytes --]
next prev parent reply other threads:[~2018-03-24 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 0:33 Abderrahmane Benbachir
2018-03-24 14:11 ` kbuild test robot [this message]
2018-03-24 15:14 ` kbuild test robot
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=201803242225.CpaSAi5v%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=abderrahmane.benbachir@polymtl.ca \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®