From: kbuild test robot <lkp@intel.com>
To: Viktor Rosendahl <viktor.rosendahl@gmail.com>
Cc: kbuild-all@01.org, Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Joel Fernandes <joel@joelfernandes.org>,
Peter Zijlstra <peterz@infradead.org>,
Viktor Rosendahl <viktor.rosendahl@gmail.com>
Subject: Re: [PATCH v5 4/4] ftrace: Add an option for tracing console latencies
Date: Wed, 4 Sep 2019 13:02:47 +0800 [thread overview]
Message-ID: <201909041221.bnLbiM3a%lkp@intel.com> (raw)
In-Reply-To: <20190903132602.3440-5-viktor.rosendahl@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi Viktor,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc7 next-20190903]
[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/Viktor-Rosendahl/Some-new-features-for-the-preempt-irqsoff-tracers/20190904-083632
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from kernel/events/hw_breakpoint.c:20:0:
>> include/linux/irqflags.h:71:9: error: unknown type name 'bool'
extern bool console_tracing_disabled(void);
^~~~
vim +/bool +71 include/linux/irqflags.h
66
67 #if defined(CONFIG_IRQSOFF_TRACER) || \
68 defined(CONFIG_PREEMPT_TRACER)
69 extern void stop_critical_timings(void);
70 extern void start_critical_timings(void);
> 71 extern bool console_tracing_disabled(void);
72
---
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: 51785 bytes --]
prev parent reply other threads:[~2019-09-04 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 13:25 [PATCH v5 0/4] Some new features for the preempt/irqsoff tracers Viktor Rosendahl
2019-09-03 13:25 ` [PATCH v5 1/4] ftrace: Implement fs notification for tracing_max_latency Viktor Rosendahl
2019-09-04 4:00 ` Joel Fernandes
2019-09-04 8:19 ` Peter Zijlstra
2019-09-04 13:42 ` Joel Fernandes
2019-09-04 18:17 ` Viktor Rosendahl
2019-09-04 10:21 ` Paul E. McKenney
2019-09-04 8:20 ` Peter Zijlstra
2019-09-04 11:37 ` Steven Rostedt
2019-09-04 11:39 ` Steven Rostedt
2019-09-04 19:00 ` Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger Viktor Rosendahl
2019-09-04 11:42 ` Steven Rostedt
2019-09-04 19:10 ` Viktor Rosendahl
2019-09-05 16:52 ` Steven Rostedt
2019-09-05 18:27 ` Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 3/4] Add the latency-collector to tools Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 4/4] ftrace: Add an option for tracing console latencies Viktor Rosendahl
2019-09-04 5:02 ` kbuild test robot [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=201909041221.bnLbiM3a%lkp@intel.com \
--to=lkp@intel.com \
--cc=joel@joelfernandes.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=viktor.rosendahl@gmail.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
Powered by JetHome