[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250224162048.7806bb1d@canb.auug.org.au>
Date: Mon, 24 Feb 2025 16:20:48 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Shawn Lin <shawn.lin@...k-chips.com>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, "Martin K. Petersen"
<martin.petersen@...cle.com>
Subject: Re: linux-next: build failure after merge of the pmdomain tree
Hi all,
On Mon, 24 Feb 2025 12:23:18 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 20 Feb 2025 11:33:38 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > 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.
>
> I am still seeing this build failure.
And now that commit from the pmdomain tree has been merged into the
scsi-mkp tree and so the build failure happens there as well.
I have used the scsi-mkp tree from next-20250221 for today.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists