From: kernel test robot <lkp@intel.com>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Stephen Boyd <swboyd@chromium.org>
Subject: [jic23-iio:testing 3/5] drivers/iio/proximity/sx_common.c:437:55: error: implicit declaration of function 'acpi_device_hid'; did you mean 'dmi_device_id'?
Date: Mon, 6 Feb 2023 02:08:10 +0800 [thread overview]
Message-ID: <202302060132.vAIoV9ew-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
head: 1693e893f058e96fdaccbdb4bb42970811ac9ec6
commit: fef38680d38d39f6f574db2c77df3de215f08e7d [3/5] iio: proximity: sx_common: Add old register mapping
config: arc-randconfig-r043-20230205 (https://download.01.org/0day-ci/archive/20230206/202302060132.vAIoV9ew-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?id=fef38680d38d39f6f574db2c77df3de215f08e7d
git remote add jic23-iio https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
git fetch --no-tags jic23-iio testing
git checkout fef38680d38d39f6f574db2c77df3de215f08e7d
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash drivers/iio/proximity/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
drivers/iio/proximity/sx_common.c: In function 'sx_common_get_raw_register_config':
>> drivers/iio/proximity/sx_common.c:437:55: error: implicit declaration of function 'acpi_device_hid'; did you mean 'dmi_device_id'? [-Werror=implicit-function-declaration]
437 | snprintf(prop, ARRAY_SIZE(prop), "%s,reg_%s", acpi_device_hid(adev), reg_def->property);
| ^~~~~~~~~~~~~~~
| dmi_device_id
>> drivers/iio/proximity/sx_common.c:437:44: warning: format '%s' expects argument of type 'char *', but argument 4 has type 'int' [-Wformat=]
437 | snprintf(prop, ARRAY_SIZE(prop), "%s,reg_%s", acpi_device_hid(adev), reg_def->property);
| ~^ ~~~~~~~~~~~~~~~~~~~~~
| | |
| char * int
| %d
cc1: some warnings being treated as errors
vim +437 drivers/iio/proximity/sx_common.c
426
427 void sx_common_get_raw_register_config(struct device *dev,
428 struct sx_common_reg_default *reg_def)
429 {
430 struct acpi_device *adev = ACPI_COMPANION(dev);
431 u32 raw = 0, ret;
432 char prop[80];
433
434 if (!reg_def->property || !adev)
435 return;
436
> 437 snprintf(prop, ARRAY_SIZE(prop), "%s,reg_%s", acpi_device_hid(adev), reg_def->property);
438 ret = device_property_read_u32(dev, prop, &raw);
439 if (ret)
440 return;
441
442 reg_def->def = raw;
443 }
444 EXPORT_SYMBOL_NS_GPL(sx_common_get_raw_register_config, SEMTECH_PROX);
445
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-05 18:08 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=202302060132.vAIoV9ew-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gwendal@chromium.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=swboyd@chromium.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 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.