From: kernel test robot <lkp@intel.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>, mpe@ellerman.id.au
Cc: mikey@neuling.org, mikey@linux.ibm.com, kbuild-all@lists.01.org,
maddy@linux.vnet.ibm.com, atrajeev@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 6/7] powerpc/perf: power10 Performance Monitoring support
Date: Fri, 5 Jun 2020 18:29:47 +0800 [thread overview]
Message-ID: <202006051820.ZDamUMQd%lkp@intel.com> (raw)
In-Reply-To: <1591343830-8286-7-git-send-email-atrajeev@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
Hi Athira,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on powerpc/next]
[also build test WARNING on next-20200605]
[cannot apply to kvm-ppc/kvm-ppc-next mpe/next v5.7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Athira-Rajeev/powerpc-perf-Add-support-for-power10-PMU-Hardware/20200605-161850
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
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
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> arch/powerpc/perf/power10-pmu.c:405:5: warning: no previous prototype for 'init_power10_pmu' [-Wmissing-prototypes]
405 | int init_power10_pmu(void)
| ^~~~~~~~~~~~~~~~
vim +/init_power10_pmu +405 arch/powerpc/perf/power10-pmu.c
404
> 405 int init_power10_pmu(void)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66059 bytes --]
next prev parent reply other threads:[~2020-06-05 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 7:57 [PATCH 0/7] powerpc/perf: Add support for power10 PMU Hardware Athira Rajeev
2020-06-05 7:57 ` [PATCH 1/7] powerpc/perf: Add support for ISA3.1 PMU SPRs Athira Rajeev
2020-06-05 7:57 ` [PATCH 2/7] KVM: PPC: Book3S HV: Save/restore new PMU registers Athira Rajeev
2020-06-05 7:57 ` [PATCH 3/7] powerpc/xmon: Add PowerISA v3.1 PMU SPRs Athira Rajeev
2020-06-05 7:57 ` [PATCH 4/7] powerpc/perf: Add power10_feat to dt_cpu_ftrs Athira Rajeev
2020-06-05 7:57 ` [PATCH 5/7] powerpc/perf: Update Power PMU cache_events to u64 type Athira Rajeev
2020-06-05 7:57 ` [PATCH 6/7] powerpc/perf: power10 Performance Monitoring support Athira Rajeev
2020-06-05 10:29 ` kernel test robot [this message]
2020-06-05 7:57 ` [PATCH 7/7] powerpc/perf: support BHRB disable bit and new filtering modes Athira Rajeev
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=202006051820.ZDamUMQd%lkp@intel.com \
--to=lkp@intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mikey@linux.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).