public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the pmdomain tree
Date: Thu, 20 Feb 2025 11:33:38 +1100	[thread overview]
Message-ID: <20250220113338.60ba2290@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hi all,

After merging the pmdomain tree, today's linux-next build (x86_64
allmodconfig) failed like this:

x86_64-linux-gnu-ld: vmlinux.o: in function `rockchip_do_pmu_set_power_domain':
pm-domains.c:(.text+0x19aa103): undefined reference to `arm_smccc_1_1_get_conduit'

Caused by commit

  61eeb9678789 ("pmdomain: rockchip: Check if SMC could be handled by TA")

$ grep CONFIG_HAVE_ARM_SMCCC_DISCOVERY .config
$

I have used the pmdomain tree from next-20250219 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-02-20  0:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  0:33 Stephen Rothwell [this message]
2025-02-20  1:53 ` linux-next: build failure after merge of the pmdomain tree Shawn Lin
2025-02-24  1:23 ` Stephen Rothwell
2025-02-24  5:20   ` Stephen Rothwell
2025-02-24 12:16     ` Ulf Hansson
2025-02-25  0:34       ` Martin K. Petersen
2025-02-27 15:56       ` Geert Uytterhoeven
2025-02-27 16:16         ` Heiko Stübner
2025-02-27 17:05           ` Geert Uytterhoeven
2025-02-28  9:01             ` Heiko Stübner
2025-02-28  9:41               ` Geert Uytterhoeven
2025-02-28 12:59               ` Ulf Hansson
  -- strict thread matches above, loose matches on Subject: below --
2025-10-22 23:30 Stephen Rothwell

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=20250220113338.60ba2290@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.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