From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-gpio@vger.kernel.org
Subject: [linusw-gpio:gpiochip-no-driver-h 5/5] arch/arm/mach-orion5x/board-rd88f5182.c:107:6: error: call to undeclared function 'of_machine_is_compatible'; ISO C99 and later do not support implicit function declarations
Date: Sun, 29 Jan 2023 00:32:37 +0800 [thread overview]
Message-ID: <202301290051.LqXniYxY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git gpiochip-no-driver-h
head: df771cce328bbd37333797d0df3471c2e03ecb03
commit: df771cce328bbd37333797d0df3471c2e03ecb03 [5/5] gpio: Make the legacy <linux/gpio.h> consumer-only
config: arm-mvebu_v5_defconfig (https://download.01.org/0day-ci/archive/20230129/202301290051.LqXniYxY-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 4196ca3278f78c6e19246e54ab0ecb364e37d66a)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/commit/?id=df771cce328bbd37333797d0df3471c2e03ecb03
git remote add linusw-gpio https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
git fetch --no-tags linusw-gpio gpiochip-no-driver-h
git checkout df771cce328bbd37333797d0df3471c2e03ecb03
# 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=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
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 >>):
>> arch/arm/mach-orion5x/board-rd88f5182.c:107:6: error: call to undeclared function 'of_machine_is_compatible'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
if (of_machine_is_compatible("marvell,rd-88f5182-nas"))
^
1 error generated.
vim +/of_machine_is_compatible +107 arch/arm/mach-orion5x/board-rd88f5182.c
065194a06b4187 Thomas Petazzoni 2014-04-22 104
065194a06b4187 Thomas Petazzoni 2014-04-22 105 static int __init rd88f5182_pci_init(void)
065194a06b4187 Thomas Petazzoni 2014-04-22 106 {
065194a06b4187 Thomas Petazzoni 2014-04-22 @107 if (of_machine_is_compatible("marvell,rd-88f5182-nas"))
065194a06b4187 Thomas Petazzoni 2014-04-22 108 pci_common_init(&rd88f5182_pci);
065194a06b4187 Thomas Petazzoni 2014-04-22 109
065194a06b4187 Thomas Petazzoni 2014-04-22 110 return 0;
065194a06b4187 Thomas Petazzoni 2014-04-22 111 }
065194a06b4187 Thomas Petazzoni 2014-04-22 112
:::::: The code at line 107 was first introduced by commit
:::::: 065194a06b4187f9c1f4a37951904534291fb85b ARM: orion5x: convert RD-88F5182 to Device Tree
:::::: TO: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
:::::: CC: Jason Cooper <jason@lakedaemon.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-01-28 16:32 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=202301290051.LqXniYxY-lkp@intel.com \
--to=lkp@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).