From: kernel test robot <lkp@intel.com>
To: Even Xu <even.xu@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Jiri Kosina <jikos@kernel.org>,
Xinpeng Sun <xinpeng.sun@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: [linux-next:master 7317/7860] drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c:259:18: error: implicit declaration of function 'acpi_execute_simple_method'; did you mean 'acpi_execute_reg_methods'?
Date: Fri, 10 Jan 2025 22:52:27 +0800 [thread overview]
Message-ID: <202501102208.3QGSCARD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2b88851f583d3c4e40bcd40cfe1965241ec229dd
commit: 9d8d51735a3af40b722346931a6a1e50227df4b5 [7317/7860] HID: intel-thc-hid: intel-quickspi: Add HIDSPI protocol implementation
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20250110/202501102208.3QGSCARD-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250110/202501102208.3QGSCARD-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/202501102208.3QGSCARD-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c: In function 'acpi_tic_reset':
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c:258:18: error: implicit declaration of function 'acpi_device_handle'; did you mean 'acpi_fwnode_handle'? [-Werror=implicit-function-declaration]
258 | handle = acpi_device_handle(qsdev->acpi_dev);
| ^~~~~~~~~~~~~~~~~~
| acpi_fwnode_handle
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c:258:16: warning: assignment to 'acpi_handle' {aka 'void *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
258 | handle = acpi_device_handle(qsdev->acpi_dev);
| ^
>> drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c:259:18: error: implicit declaration of function 'acpi_execute_simple_method'; did you mean 'acpi_execute_reg_methods'? [-Werror=implicit-function-declaration]
259 | status = acpi_execute_simple_method(handle, "_RST", 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| acpi_execute_reg_methods
cc1: some warnings being treated as errors
vim +259 drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c
249
250 static int acpi_tic_reset(struct quickspi_device *qsdev)
251 {
252 acpi_status status = 0;
253 acpi_handle handle;
254
255 if (!qsdev->acpi_dev)
256 return -ENODEV;
257
258 handle = acpi_device_handle(qsdev->acpi_dev);
> 259 status = acpi_execute_simple_method(handle, "_RST", 0);
260 if (ACPI_FAILURE(status)) {
261 dev_err_once(qsdev->dev,
262 "Failed to reset device through ACPI method, ret = %d\n", status);
263 return -EIO;
264 }
265
266 return 0;
267 }
268
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-10 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501102208.3QGSCARD-lkp@intel.com \
--to=lkp@intel.com \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=xinpeng.sun@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.