From: kernel test robot <lkp@intel.com>
To: Kartik Rajput <kkartik@nvidia.com>,
lenb@kernel.org, sakari.ailus@linux.intel.com,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kartik Rajput <kkartik@nvidia.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] ACPI: bus: Use OF match data for PRP0001 matched devices
Date: Wed, 7 Jan 2026 22:11:01 +0100 [thread overview]
Message-ID: <202601072231.MPkHMWgN-lkp@intel.com> (raw)
In-Reply-To: <20260107062453.10893-1-kkartik@nvidia.com>
Hi Kartik,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on rafael-pm/bleeding-edge westeri-thunderbolt/next linus/master v6.16-rc1 next-20260107]
[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/Kartik-Rajput/ACPI-bus-Use-OF-match-data-for-PRP0001-matched-devices/20260107-142543
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20260107062453.10893-1-kkartik%40nvidia.com
patch subject: [PATCH] ACPI: bus: Use OF match data for PRP0001 matched devices
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260107/202601072231.MPkHMWgN-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260107/202601072231.MPkHMWgN-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/202601072231.MPkHMWgN-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/acpi/bus.c:1034:21: error: expected identifier or '('
1034 | struct acpi_device = ACPI_COMPANION(dev);
| ^
>> drivers/acpi/bus.c:1036:53: error: use of undeclared identifier 'adev'; did you mean 'dev'?
1036 | if (!strcmp(ACPI_DT_NAMESPACE_HID, acpi_device_hid(adev))
| ^~~~
| dev
drivers/acpi/bus.c:1030:61: note: 'dev' declared here
1030 | const void *acpi_device_get_match_data(const struct device *dev)
| ^
>> drivers/acpi/bus.c:1037:3: error: expected ')'
1037 | return acpi_of_device_get_match_data(dev);
| ^
drivers/acpi/bus.c:1036:5: note: to match this '('
1036 | if (!strcmp(ACPI_DT_NAMESPACE_HID, acpi_device_hid(adev))
| ^
3 errors generated.
vim +1034 drivers/acpi/bus.c
1029
1030 const void *acpi_device_get_match_data(const struct device *dev)
1031 {
1032 const struct acpi_device_id *acpi_ids = dev->driver->acpi_match_table;
1033 const struct acpi_device_id *match;
> 1034 struct acpi_device = ACPI_COMPANION(dev);
1035
> 1036 if (!strcmp(ACPI_DT_NAMESPACE_HID, acpi_device_hid(adev))
> 1037 return acpi_of_device_get_match_data(dev);
1038
1039 match = acpi_match_device(acpi_ids, dev);
1040 if (!match)
1041 return NULL;
1042
1043 return (const void *)match->driver_data;
1044 }
1045 EXPORT_SYMBOL_GPL(acpi_device_get_match_data);
1046
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-07 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 6:24 [PATCH] ACPI: bus: Use OF match data for PRP0001 matched devices Kartik Rajput
2026-01-07 11:42 ` Sakari Ailus
2026-01-07 12:03 ` Kartik Rajput
2026-01-07 21:11 ` kernel test robot [this message]
2026-01-07 22:25 ` kernel test robot
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=202601072231.MPkHMWgN-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.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