From: kernel test robot <lkp@intel.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v7 09/10] platform/chrome: Introduce device tree hardware prober
Date: Fri, 13 Sep 2024 23:36:12 +0800 [thread overview]
Message-ID: <202409132343.1z91h4au-lkp@intel.com> (raw)
In-Reply-To: <20240911072751.365361-10-wenst@chromium.org>
Hi Chen-Yu,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-regulator/for-next]
[also build test ERROR on next-20240913]
[cannot apply to robh/for-next wsa/i2c/for-next linus/master v6.11-rc7]
[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/Chen-Yu-Tsai/of-dynamic-Add-of_changeset_update_prop_string/20240911-153237
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link: https://lore.kernel.org/r/20240911072751.365361-10-wenst%40chromium.org
patch subject: [PATCH v7 09/10] platform/chrome: Introduce device tree hardware prober
config: arm64-randconfig-002-20240913 (https://download.01.org/0day-ci/archive/20240913/202409132343.1z91h4au-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project bf684034844c660b778f0eba103582f582b710c9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240913/202409132343.1z91h4au-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/202409132343.1z91h4au-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/platform/chrome/chromeos_of_hw_prober.c:66:8: error: call to undeclared function 'of_machine_is_compatible'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
66 | if (!of_machine_is_compatible(hw_prober_platforms[i].compatible))
| ^
drivers/platform/chrome/chromeos_of_hw_prober.c:93:7: error: call to undeclared function 'of_machine_is_compatible'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
93 | if (of_machine_is_compatible(hw_prober_platforms[i].compatible))
| ^
2 errors generated.
vim +/of_machine_is_compatible +66 drivers/platform/chrome/chromeos_of_hw_prober.c
60
61 static int chromeos_of_hw_prober_probe(struct platform_device *pdev)
62 {
63 for (size_t i = 0; i < ARRAY_SIZE(hw_prober_platforms); i++) {
64 int ret;
65
> 66 if (!of_machine_is_compatible(hw_prober_platforms[i].compatible))
67 continue;
68
69 ret = hw_prober_platforms[i].prober(&pdev->dev, hw_prober_platforms[i].data);
70 /* Ignore unrecoverable errors and keep going through other probers */
71 if (ret == -EPROBE_DEFER)
72 return ret;
73 }
74
75 return 0;
76 }
77
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-09-13 15:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240911072751.365361-10-wenst@chromium.org>]
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=202409132343.1z91h4au-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wenst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox