From: kbuild test robot <lkp@intel.com>
To: alexander.antonov@linux.intel.com, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, bgregg@netflix.com, ak@linux.intel.com,
kan.liang@linux.intel.com
Cc: kbuild-all@lists.01.org, alexander.antonov@linux.intel.com
Subject: Re: [RESEND PATCH v9 3/3] perf/x86/intel/uncore: Expose an Uncore unit to IIO PMON mapping
Date: Fri, 29 May 2020 10:27:08 +0800 [thread overview]
Message-ID: <202005291043.R1YE8qpI%lkp@intel.com> (raw)
In-Reply-To: <20200525080554.21313-4-alexander.antonov@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/perf/core]
[also build test WARNING on tip/auto-latest linus/master linux/master v5.7-rc7 next-20200528]
[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/alexander-antonov-linux-intel-com/perf-x86-Exposing-IO-stack-to-IO-PMON-mapping-through-sysfs/20200525-160819
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git c50c75e9b87946499a62bffc021e95c87a1d57cd
config: i386-randconfig-r003-20200528 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> arch/x86/events/intel/uncore_snbep.c:3737:1: warning: 'static' is not at beginning of declaration [-Wold-style-declaration]
3737 | const static struct attribute_group *skx_iio_attr_update[] = {
| ^~~~~
vim +/static +3737 arch/x86/events/intel/uncore_snbep.c
3736
> 3737 const static struct attribute_group *skx_iio_attr_update[] = {
3738 &skx_iio_mapping_group,
3739 NULL,
3740 };
3741
---
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: 45541 bytes --]
prev parent reply other threads:[~2020-05-29 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 8:05 [RESEND PATCH v9 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs alexander.antonov
2020-05-25 8:05 ` [RESEND PATCH v9 1/3] perf/x86/intel/uncore: Expose an Uncore unit to PMON mapping alexander.antonov
2020-05-25 8:05 ` [RESEND PATCH v9 2/3] perf/x86/intel/uncore: Wrap the max dies calculation into an accessor alexander.antonov
2020-05-25 8:05 ` [RESEND PATCH v9 3/3] perf/x86/intel/uncore: Expose an Uncore unit to IIO PMON mapping alexander.antonov
2020-05-29 2:27 ` 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=202005291043.R1YE8qpI%lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgregg@netflix.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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