From: kernel test robot <lkp@intel.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Joerg Roedel <jroedel@suse.de>, Hanjun Guo <guohanjun@huawei.com>
Subject: [linux-next:master 6932/13542] drivers/acpi/arm64/iort.c:1406:2: error: call to undeclared function 'iort_iommu_rmr_get_resv_regions'; ISO C99 and later do not support implicit function declarations
Date: Fri, 29 Jul 2022 13:28:51 +0800 [thread overview]
Message-ID: <202207291335.1sImjcbY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7c5e07b73ff3011c9b82d4a3286a3362b951ad2b
commit: e302eea8f49717253ac64fd45b7cc719e87fa010 [6932/13542] ACPI/IORT: Add a helper to retrieve RMR info directly
config: arm64-buildonly-randconfig-r005-20220728 (https://download.01.org/0day-ci/archive/20220729/202207291335.1sImjcbY-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 8dfaecc4c24494337933aff9d9166486ca0949f1)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e302eea8f49717253ac64fd45b7cc719e87fa010
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout e302eea8f49717253ac64fd45b7cc719e87fa010
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/acpi/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/acpi/arm64/iort.c:1406:2: error: call to undeclared function 'iort_iommu_rmr_get_resv_regions'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
iort_iommu_rmr_get_resv_regions(iommu_fwnode, NULL, head);
^
drivers/acpi/arm64/iort.c:1406:2: note: did you mean 'iort_iommu_get_resv_regions'?
drivers/acpi/arm64/iort.c:1329:6: note: 'iort_iommu_get_resv_regions' declared here
void iort_iommu_get_resv_regions(struct device *dev, struct list_head *head)
^
1 error generated.
vim +/iort_iommu_rmr_get_resv_regions +1406 drivers/acpi/arm64/iort.c
1396
1397 /**
1398 * iort_get_rmr_sids - Retrieve IORT RMR node reserved regions with
1399 * associated StreamIDs information.
1400 * @iommu_fwnode: fwnode associated with IOMMU
1401 * @head: Resereved region list
1402 */
1403 void iort_get_rmr_sids(struct fwnode_handle *iommu_fwnode,
1404 struct list_head *head)
1405 {
> 1406 iort_iommu_rmr_get_resv_regions(iommu_fwnode, NULL, head);
1407 }
1408 EXPORT_SYMBOL_GPL(iort_get_rmr_sids);
1409
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-29 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 5:28 kernel test robot [this message]
2022-07-29 8:03 ` Shameerali Kolothum Thodi
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=202207291335.1sImjcbY-lkp@intel.com \
--to=lkp@intel.com \
--cc=guohanjun@huawei.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=shameerali.kolothum.thodi@huawei.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