From: kernel test robot <lkp@intel.com>
To: Alex Elder <elder@riscstar.com>
Cc: oe-kbuild-all@lists.linux.dev, Vinod Koul <vkoul@kernel.org>,
Kishon <kishon@ti.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [phy:next 13/98] phy-spacemit-k1-pcie.c:undefined reference to `devm_clk_hw_register'
Date: Fri, 02 Jan 2026 21:02:16 +0800 [thread overview]
Message-ID: <202601022046.OKfcBo0x-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
head: add66a6673bc4aacd0ef0f3c4a51271501770b17
commit: 57e920b92724dd568526990c04e79ed54241c5fc [13/98] phy: spacemit: Introduce PCIe/combo PHY
config: s390-randconfig-r112-20260102 (https://download.01.org/0day-ci/archive/20260102/202601022046.OKfcBo0x-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260102/202601022046.OKfcBo0x-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/202601022046.OKfcBo0x-lkp@intel.com/
Note: the phy/next HEAD add66a6673bc4aacd0ef0f3c4a51271501770b17 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
s390-linux-ld: drivers/phy/phy-spacemit-k1-pcie.o: in function `k1_pcie_phy_probe':
>> phy-spacemit-k1-pcie.c:(.text+0x19ec): undefined reference to `devm_clk_hw_register'
>> s390-linux-ld: phy-spacemit-k1-pcie.c:(.text+0x1a7a): undefined reference to `devm_clk_hw_get_clk'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-02 13:03 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=202601022046.OKfcBo0x-lkp@intel.com \
--to=lkp@intel.com \
--cc=elder@riscstar.com \
--cc=kishon@ti.com \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.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.