linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: linuxppc-dev@lists.ozlabs.org, kbuild-all@01.org
Subject: Re: [PATCH 2/2] powerpc/perf: Add generic compat mode pmu driver
Date: Tue, 2 Apr 2019 09:14:16 +0530	[thread overview]
Message-ID: <77e1d405-210a-9f23-3f00-32a3d2e57b51@linux.vnet.ibm.com> (raw)
In-Reply-To: <201904011812.L1ZHWkLf%lkp@intel.com>


On 01/04/19 4:00 PM, kbuild test robot wrote:
> Hi Madhavan,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on powerpc/next]
> [also build test ERROR on v5.1-rc3 next-20190401]
> [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/Madhavan-Srinivasan/powerpc-perf-init-platform-pmu-driver-from-core-book3s/20190401-104458
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
> config: powerpc-pmac32_defconfig (attached as .config)
> compiler: powerpc-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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.2.0 make.cross ARCH=powerpc
>
> All errors (new ones prefixed by >>):
>
>     arch/powerpc/perf/core-book3s.o: In function `init_ppc64_pmu':
>     core-book3s.c:(.init.text+0xc): undefined reference to `init_power5_pmu'
>     core-book3s.c:(.init.text+0x18): undefined reference to `init_power5p_pmu'
>     core-book3s.c:(.init.text+0x24): undefined reference to `init_power6_pmu'
>     core-book3s.c:(.init.text+0x30): undefined reference to `init_power7_pmu'
>     core-book3s.c:(.init.text+0x3c): undefined reference to `init_power8_pmu'
>     core-book3s.c:(.init.text+0x48): undefined reference to `init_power9_pmu'
>     core-book3s.c:(.init.text+0x54): undefined reference to `init_ppc970_pmu'
>>> core-book3s.c:(.init.text+0x6c): undefined reference to `init_generic_compat_pmu'
My bad, missed to add the code under CONFIG_64.
will send out a newer version.

Maddy

> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


  reply	other threads:[~2019-04-02  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31 19:18 [PATCH 1/2] powerpc/perf: init platform pmu driver from core-book3s Madhavan Srinivasan
2019-03-31 19:18 ` [PATCH 2/2] powerpc/perf: Add generic compat mode pmu driver Madhavan Srinivasan
2019-04-01 10:30   ` kbuild test robot
2019-04-02  3:44     ` Madhavan Srinivasan [this message]
2019-04-01  9:55 ` [PATCH 1/2] powerpc/perf: init platform pmu driver from core-book3s kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2019-04-04 11:54 [PATCH v2 1/2] powerpc/perf: init pmu " Madhavan Srinivasan
2019-04-04 11:54 ` [PATCH 2/2] powerpc/perf: Add generic compat mode pmu driver Madhavan Srinivasan
2019-05-03  6:59   ` Michael Ellerman

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=77e1d405-210a-9f23-3f00-32a3d2e57b51@linux.vnet.ibm.com \
    --to=maddy@linux.vnet.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.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).