public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH/RFC 2/3] pmdomain: core: Avoid earlycon power-down
Date: Tue, 28 May 2024 11:20:13 +0800	[thread overview]
Message-ID: <202405281126.rl6q4ObG-lkp@intel.com> (raw)
In-Reply-To: <7c5c0c8a10b8f755e5a75c7836b43cac63762eec.1716811405.git.geert+renesas@glider.be>

Hi Geert,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus rafael-pm/linux-next rafael-pm/bleeding-edge geert-renesas-devel/next linus/master v6.10-rc1 next-20240523]
[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/Geert-Uytterhoeven/earlycon-Export-clock-and-PM-Domain-info-from-FDT/20240527-204346
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link:    https://lore.kernel.org/r/7c5c0c8a10b8f755e5a75c7836b43cac63762eec.1716811405.git.geert%2Brenesas%40glider.be
patch subject: [PATCH/RFC 2/3] pmdomain: core: Avoid earlycon power-down
config: arm64-randconfig-002-20240528 (https://download.01.org/0day-ci/archive/20240528/202405281126.rl6q4ObG-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240528/202405281126.rl6q4ObG-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/202405281126.rl6q4ObG-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: undefined symbol: earlycon_power_domains
   >>> referenced by core.c
   >>>               drivers/pmdomain/core.o:(of_genpd_add_provider_simple) in archive vmlinux.a
   >>> referenced by core.c
   >>>               drivers/pmdomain/core.o:(of_genpd_add_provider_simple) in archive vmlinux.a
   >>> referenced by core.c
   >>>               drivers/pmdomain/core.o:(of_genpd_add_provider_onecell) in archive vmlinux.a
   >>> referenced 1 more times
--
>> ld.lld: error: undefined symbol: earlycon_power_domains_ncells
   >>> referenced by core.c
   >>>               drivers/pmdomain/core.o:(of_genpd_add_provider_onecell) in archive vmlinux.a
   >>> referenced by core.c
   >>>               drivers/pmdomain/core.o:(of_genpd_add_provider_onecell) in archive vmlinux.a

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

       reply	other threads:[~2024-05-28  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7c5c0c8a10b8f755e5a75c7836b43cac63762eec.1716811405.git.geert+renesas@glider.be>
2024-05-28  3:20 ` kernel test robot [this message]
2024-05-29  8:59   ` [PATCH/RFC 2/3] pmdomain: core: Avoid earlycon power-down Geert Uytterhoeven

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=202405281126.rl6q4ObG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geert+renesas@glider.be \
    --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