From: kernel test robot <lkp@intel.com>
To: Xu Yang <xu.yang_2@nxp.com>,
frank.li@nxp.com, will@kernel.org, mark.rutland@arm.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
john.g.garry@oracle.com, jolsa@kernel.org, namhyung@kernel.org,
irogers@google.com
Cc: oe-kbuild-all@lists.linux.dev, mike.leach@linaro.org,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, adrian.hunter@intel.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v11 2/8] perf: imx_perf: add macro definitions for parsing config attr
Date: Tue, 28 May 2024 21:15:39 +0800 [thread overview]
Message-ID: <202405282005.xvD134Kz-lkp@intel.com> (raw)
In-Reply-To: <20240528160523.1695953-2-xu.yang_2@nxp.com>
Hi Xu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on perf-tools-next/perf-tools-next]
[also build test WARNING on tip/perf/core perf-tools/perf-tools linus/master v6.10-rc1 next-20240528]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Xu-Yang/perf-imx_perf-add-macro-definitions-for-parsing-config-attr/20240528-160104
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/20240528160523.1695953-2-xu.yang_2%40nxp.com
patch subject: [PATCH v11 2/8] perf: imx_perf: add macro definitions for parsing config attr
config: arm64-randconfig-004-20240528 (https://download.01.org/0day-ci/archive/20240528/202405282005.xvD134Kz-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240528/202405282005.xvD134Kz-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405282005.xvD134Kz-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/perf/fsl_imx9_ddr_perf.c:46: warning: "CONFIG_COUNTER" redefined
46 | #define CONFIG_COUNTER GENMASK(15, 8)
|
In file included from include/linux/kconfig.h:5,
from <command-line>:
./include/generated/autoconf.h:433: note: this is the location of the previous definition
433 | #define CONFIG_COUNTER 1
|
vim +/CONFIG_COUNTER +46 drivers/perf/fsl_imx9_ddr_perf.c
44
45 #define CONFIG_EVENT GENMASK(7, 0)
> 46 #define CONFIG_COUNTER GENMASK(15, 8)
47
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-28 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 16:05 [PATCH v11 1/8] dt-bindings: perf: fsl-imx-ddr: Add i.MX95 compatible Xu Yang
2024-05-28 16:05 ` [PATCH v11 2/8] perf: imx_perf: add macro definitions for parsing config attr Xu Yang
2024-05-28 13:15 ` kernel test robot
2024-05-28 13:15 ` kernel test robot [this message]
2024-05-28 16:05 ` [PATCH v11 3/8] perf: imx_perf: let the driver manage the counter usage rather the user Xu Yang
2024-05-28 16:05 ` [PATCH v11 4/8] perf: imx_perf: refactor driver for imx93 Xu Yang
2024-05-28 16:05 ` [PATCH v11 5/8] perf: imx_perf: fix counter start and config sequence Xu Yang
2024-05-28 16:05 ` [PATCH v11 6/8] perf: imx_perf: add support for i.MX95 platform Xu Yang
2024-05-28 16:05 ` [PATCH v11 7/8] perf vendor events arm64:: Add i.MX93 DDR Performance Monitor metrics Xu Yang
2024-05-28 16:05 ` [PATCH v11 8/8] perf vendor events arm64:: Add i.MX95 " Xu Yang
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=202405282005.xvD134Kz-lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
--cc=xu.yang_2@nxp.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).