From: kernel test robot <lkp@intel.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 5/6] platform/chrome: Introduce device tree hardware prober
Date: Fri, 9 Aug 2024 16:55:31 +0800 [thread overview]
Message-ID: <202408091602.lbNPJAzJ-lkp@intel.com> (raw)
In-Reply-To: <20240808095931.2649657-6-wenst@chromium.org>
Hi Chen-Yu,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on broonie-regulator/for-next wsa/i2c/for-next linus/master v6.11-rc2 next-20240809]
[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/20240808-181544
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20240808095931.2649657-6-wenst%40chromium.org
patch subject: [PATCH v4 5/6] platform/chrome: Introduce device tree hardware prober
config: sh-randconfig-002-20240809 (https://download.01.org/0day-ci/archive/20240809/202408091602.lbNPJAzJ-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240809/202408091602.lbNPJAzJ-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/202408091602.lbNPJAzJ-lkp@intel.com/
All errors (new ones prefixed by >>):
sh4-linux-ld: drivers/platform/chrome/chromeos_of_hw_prober.o: in function `chromeos_i2c_component_prober':
>> chromeos_of_hw_prober.c:(.text+0x2c): undefined reference to `i2c_of_probe_component'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-09 8:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:59 [PATCH v4 0/6] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-08-08 9:59 ` [PATCH v4 1/6] of: dynamic: Add of_changeset_update_prop_string Chen-Yu Tsai
2024-08-13 11:11 ` Andy Shevchenko
2024-08-13 19:18 ` Rob Herring
2024-08-14 4:26 ` Chen-Yu Tsai
2024-08-08 9:59 ` [PATCH v4 2/6] regulator: Add regulator_of_get_optional() for pure DT regulator lookup Chen-Yu Tsai
2024-08-13 11:22 ` Andy Shevchenko
2024-08-08 9:59 ` [PATCH v4 3/6] i2c: Introduce OF component probe function Chen-Yu Tsai
2024-08-13 11:26 ` Andy Shevchenko
2024-08-15 9:55 ` Chen-Yu Tsai
2024-08-08 9:59 ` [PATCH v4 4/6] i2c: of-prober: Add GPIO and regulator support Chen-Yu Tsai
2024-08-13 11:41 ` Andy Shevchenko
2024-08-14 11:34 ` Chen-Yu Tsai
2024-08-14 13:53 ` Andy Shevchenko
2024-08-21 9:44 ` Chen-Yu Tsai
2024-08-08 9:59 ` [PATCH v4 5/6] platform/chrome: Introduce device tree hardware prober Chen-Yu Tsai
2024-08-09 8:55 ` kernel test robot [this message]
2024-08-13 11:46 ` Andy Shevchenko
2024-08-14 10:10 ` Chen-Yu Tsai
2024-08-14 13:41 ` Andy Shevchenko
2024-08-08 9:59 ` [PATCH v4 6/6] arm64: dts: mediatek: mt8173-elm-hana: Mark touchscreens and trackpads as fail Chen-Yu Tsai
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=202408091602.lbNPJAzJ-lkp@intel.com \
--to=lkp@intel.com \
--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 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.