From: kbuild test robot <lkp@intel.com>
To: Jiaxing Wang <hello.wjx@gmail.com>
Cc: kbuild-all@01.org, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Jiaxing Wang <hello.wjx@gmail.com>
Subject: Re: [PATCH 2/3] tracing: Make tracing work when debugfs is not compiled or initialized.
Date: Sun, 18 Oct 2015 22:32:26 +0800 [thread overview]
Message-ID: <201510182221.OYWO92iw%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445169490-18315-3-git-send-email-hello.wjx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
Hi Jiaxing,
[auto build test ERROR on tip/perf/core -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Jiaxing-Wang/Some-tracing-fixes/20151018-200252
config: arm-omap2plus_defconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All error/warnings (new ones prefixed by >>):
kernel/trace/trace.c: In function 'tracing_init_dentry':
>> kernel/trace/trace.c:6737:3: error: implicit declaration of function 'debugfs_create_automount' [-Werror=implicit-function-declaration]
traced = debugfs_create_automount("tracing", NULL,
^
>> kernel/trace/trace.c:6737:10: warning: assignment makes pointer from integer without a cast
traced = debugfs_create_automount("tracing", NULL,
^
cc1: some warnings being treated as errors
vim +/debugfs_create_automount +6737 kernel/trace/trace.c
6731 /*
6732 * As there may still be users that expect the tracing
6733 * files to exist in debugfs/tracing, we must automount
6734 * the tracefs file system there, so older tools still
6735 * work with the newer kerenl.
6736 */
> 6737 traced = debugfs_create_automount("tracing", NULL,
6738 trace_automount, NULL);
6739 if (!traced)
6740 pr_warn_once("Could not create debugfs directory 'tracing'\n");
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24643 bytes --]
next prev parent reply other threads:[~2015-10-18 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 11:58 [PATCH 0/3] Some tracing fixes Jiaxing Wang
2015-10-18 11:58 ` [PATCH 1/3] tracing: Update instance_rmdir() to use tracefs_remove_recursive Jiaxing Wang
2015-10-18 11:58 ` [PATCH 2/3] tracing: Make tracing work when debugfs is not compiled or initialized Jiaxing Wang
2015-10-18 14:32 ` kbuild test robot [this message]
2015-10-19 1:54 ` Jiaxing Wang
2015-11-02 14:16 ` Steven Rostedt
2015-11-04 1:11 ` [PATCH RESEND] " Jiaxing Wang
2015-11-04 15:03 ` Steven Rostedt
2015-11-04 18:54 ` Greg Kroah-Hartman
2015-11-04 20:32 ` Steven Rostedt
2015-11-05 5:23 ` Jiaxing Wang
2015-11-05 15:54 ` Steven Rostedt
2015-11-06 8:02 ` Jiaxing Wang
2015-11-06 8:04 ` [PATCH] tracing: Make tracing work when debugfs is not configured in Jiaxing Wang
2015-10-18 11:58 ` [PATCH 3/3] tracing: Apply tracer specific options from kernel command line Jiaxing Wang
2015-11-02 19:04 ` Steven Rostedt
2015-11-04 1:14 ` [PATCH v2] " Jiaxing Wang
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=201510182221.OYWO92iw%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hello.wjx@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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®