From: kernel test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
coresight@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] coresight: trbe: Enable ACPI based TRBE devices
Date: Sat, 5 Aug 2023 22:02:23 +0800 [thread overview]
Message-ID: <202308052123.uqR35d19-lkp@intel.com> (raw)
In-Reply-To: <20230728112733.359620-4-anshuman.khandual@arm.com>
Hi Anshuman,
kernel test robot noticed the following build errors:
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on arm/for-next soc/for-next linus/master arm/fixes v6.5-rc4 next-20230804]
[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/Anshuman-Khandual/arm_pmu-acpi-Add-a-representative-platform-device-for-TRBE/20230728-192939
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
patch link: https://lore.kernel.org/r/20230728112733.359620-4-anshuman.khandual%40arm.com
patch subject: [PATCH 3/3] coresight: trbe: Enable ACPI based TRBE devices
config: arm64-randconfig-r021-20230731 (https://download.01.org/0day-ci/archive/20230805/202308052123.uqR35d19-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230805/202308052123.uqR35d19-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/202308052123.uqR35d19-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/hwtracing/coresight/coresight-trbe.c:1549:14: error: use of undeclared identifier 'arm_trbe_acpi_match'; did you mean 'arm_trbe_of_match'?
.id_table = arm_trbe_acpi_match,
^~~~~~~~~~~~~~~~~~~
arm_trbe_of_match
drivers/hwtracing/coresight/coresight-trbe.c:1534:34: note: 'arm_trbe_of_match' declared here
static const struct of_device_id arm_trbe_of_match[] = {
^
>> drivers/hwtracing/coresight/coresight-trbe.c:1549:14: error: incompatible pointer types initializing 'const struct platform_device_id *' with an expression of type 'const struct of_device_id[2]' [-Werror,-Wincompatible-pointer-types]
.id_table = arm_trbe_acpi_match,
^~~~~~~~~~~~~~~~~~~
2 errors generated.
vim +1549 drivers/hwtracing/coresight/coresight-trbe.c
1547
1548 static struct platform_driver arm_trbe_driver = {
> 1549 .id_table = arm_trbe_acpi_match,
1550 .driver = {
1551 .name = DRVNAME,
1552 .of_match_table = of_match_ptr(arm_trbe_of_match),
1553 .suppress_bind_attrs = true,
1554 },
1555 .probe = arm_trbe_device_probe,
1556 .remove = arm_trbe_device_remove,
1557 };
1558
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-08-05 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 11:27 [PATCH 0/3] coresight: trbe: Enable ACPI based devices Anshuman Khandual
2023-07-28 11:27 ` [PATCH 1/3] arm_pmu: acpi: Add a representative platform device for TRBE Anshuman Khandual
2023-07-28 14:40 ` Will Deacon
2023-07-31 12:08 ` Anshuman Khandual
2023-07-31 14:59 ` Will Deacon
2023-08-01 3:35 ` Anshuman Khandual
2023-08-01 7:38 ` Will Deacon
2023-08-01 8:53 ` Anshuman Khandual
2023-07-28 11:27 ` [PATCH 2/3] coresight: trbe: Add a representative coresight_platform_data " Anshuman Khandual
2023-07-28 11:27 ` [PATCH 3/3] coresight: trbe: Enable ACPI based TRBE devices Anshuman Khandual
2023-08-05 14:02 ` kernel 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=202308052123.uqR35d19-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mike.leach@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®