mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org,
	Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] ftrace: filter: Match dot symbols when searching functions on ppc64.
Date: Sat, 2 Apr 2016 03:51:21 +0800	[thread overview]
Message-ID: <201604020331.kEOeyhX0%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459480972-20238-1-git-send-email-bauerman@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

Hi Thiago,

[auto build test ERROR on v4.6-rc1]
[also build test ERROR on next-20160401]
[cannot apply to tip/perf/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Thiago-Jung-Bauermann/ftrace-filter-Match-dot-symbols-when-searching-functions-on-ppc64/20160401-112617
config: powerpc-ppc6xx_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=powerpc 

All errors (new ones prefixed by >>):

   In file included from include/linux/ftrace.h:20:0,
                    from include/linux/perf_event.h:47,
                    from include/linux/trace_events.h:9,
                    from include/trace/syscall.h:6,
                    from include/linux/syscalls.h:81,
                    from arch/powerpc/kernel/pci-common.c:29:
>> arch/powerpc/include/asm/ftrace.h:62:5: error: "CONFIG_PPC64" is not defined [-Werror=undef]
    #if CONFIG_PPC64 && (!defined(_CALL_ELF) || _CALL_ELF != 2)
        ^
   cc1: all warnings being treated as errors

vim +/CONFIG_PPC64 +62 arch/powerpc/include/asm/ftrace.h

    56	
    57	struct dyn_arch_ftrace {
    58		struct module *mod;
    59	};
    60	#endif /*  CONFIG_DYNAMIC_FTRACE */
    61	
  > 62	#if CONFIG_PPC64 && (!defined(_CALL_ELF) || _CALL_ELF != 2)
    63	#define ARCH_HAS_FTRACE_MATCH_ADJUST
    64	static inline void arch_ftrace_match_adjust(char **str, char *search)
    65	{

---
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: 27992 bytes --]

  reply	other threads:[~2016-04-01 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01  3:22 Thiago Jung Bauermann
2016-04-01 19:51 ` kbuild test robot [this message]
2016-04-01 21:28   ` Thiago Jung Bauermann
2016-04-14  0:39     ` Thiago Jung Bauermann
2016-04-14  3:51       ` Steven Rostedt
2016-04-14  7:11 ` Michael Ellerman
2016-04-14 10:58   ` Steven Rostedt
2016-04-14 23:48     ` Thiago Jung Bauermann

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=201604020331.kEOeyhX0%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --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®