Re: linux-next: build failure after merge of the rpmsg tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 1 Jul 2024 at 10:26, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
>
> Hi Mark,
>
> On Wed, 26 Jun 2024 19:44:24 +0100 Mark Brown <broonie@xxxxxxxxxx> wrote:
> >
> > Hi all,
> >
> > After merging the rpmsg tree, today's linux-next build (KCONFIG_NAME)
> > failed like this:
> >
> > ERROR: modpost: "__auxiliary_driver_register" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "servreg_loc_pfr_resp_ei" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "auxiliary_driver_unregister" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "servreg_get_domain_list_resp_ei" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "servreg_get_domain_list_req_ei" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "servreg_loc_pfr_req_ei" [drivers/soc/qcom/qcom_pd_mapper.ko] undefined!
> > ERROR: modpost: "auxiliary_device_init" [drivers/remoteproc/qcom_common.ko] undefined!
> > ERROR: modpost: "__auxiliary_device_add" [drivers/remoteproc/qcom_common.ko] undefined!
> >
> > Caused by commit
> >
> >   5b9f51b200dcb2c3924 ("remoteproc: qcom: enable in-kernel PD mapper")
> >
> > and likely others, I didn't look too hard.  I have used the tree from
> > 20240625 instead.
>
> I am still seeing this build failure in the arm multi_v7_defconfig build.

This should be fixed by
https://lore.kernel.org/linux-arm-msm/20240626-qcom-pd-mapper-fix-deps-v1-0-644678dc4663@xxxxxxxxxx/
, hopefully Bjorn can pick it up.

-- 
With best wishes
Dmitry




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux