From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bjorn Andersson <andersson@kernel•org>,
Mathieu Poirier <mathieu.poirier@linaro•org>
Cc: Mark Brown <broonie@kernel•org>,
Chris Lew <quic_clew@quicinc•com>,
Steev Klimaszewski <steev@kali•org>,
Neil Armstrong <neil.armstrong@linaro•org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the rpmsg tree
Date: Mon, 1 Jul 2024 17:26:55 +1000 [thread overview]
Message-ID: <20240701172655.3db48d51@canb.auug.org.au> (raw)
In-Reply-To: <ZnxhiKAYvoqNIywH@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Hi Mark,
On Wed, 26 Jun 2024 19:44:24 +0100 Mark Brown <broonie@kernel•org> 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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-01 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 18:44 linux-next: build failure after merge of the rpmsg tree Mark Brown
2024-07-01 7:26 ` Stephen Rothwell [this message]
2024-07-01 10:08 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 7:02 Stephen Rothwell
2023-01-30 8:51 ` Joerg Roedel
2020-10-15 4:55 Stephen Rothwell
2019-02-22 5:18 Stephen Rothwell
2019-02-22 12:50 ` Christoph Hellwig
2019-02-22 14:02 ` Loic PALLARDY
2018-04-26 3:33 Stephen Rothwell
2018-04-26 3:46 ` Bjorn Andersson
2017-08-31 6:54 Stephen Rothwell
2017-08-31 17:47 ` Bjorn Andersson
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=20240701172655.3db48d51@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andersson@kernel$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mathieu.poirier@linaro$(echo .)org \
--cc=neil.armstrong@linaro$(echo .)org \
--cc=quic_clew@quicinc$(echo .)com \
--cc=steev@kali$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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