From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Maximilian Luz <luzmaximilian@gmail•com>,
linux-arm-msm@vger•kernel.org
Subject: Re: linux-next: Tree for Sep 15 (drivers/firmware/qcom)
Date: Fri, 15 Sep 2023 12:30:27 -0700 [thread overview]
Message-ID: <9f156fa6-e5aa-4cb2-ab2b-b67fd8fc4840@infradead.org> (raw)
In-Reply-To: <20230915120127.1bc03420@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
On 9/14/23 19:01, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230914:
>
> The btrfs tree gained a conflist against the mm tree.
>
> The device-mapper tree gained a build failure so I used the version
> from next-20230914.
>
> The kspp tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 5026
> 2501 files changed, 391711 insertions(+), 34318 deletions(-)
>
> ----------------------------------------------------------------------------
on loongarch:
loongarch64-linux-ld: drivers/firmware/qcom_qseecom.o: in function `.L16':
qcom_qseecom.c:(.text+0x150): undefined reference to `auxiliary_device_init'
loongarch64-linux-ld: qcom_qseecom.c:(.text+0x168): undefined reference to `__auxiliary_device_add'
loongarch64-linux-ld: drivers/firmware/qcom_qseecom_uefisecapp.o: in function `qcom_uefisecapp_driver_init':
qcom_qseecom_uefisecapp.c:(.init.text+0x30): undefined reference to `__auxiliary_driver_register'
loongarch64-linux-ld: drivers/firmware/qcom_qseecom_uefisecapp.o: in function `qcom_uefisecapp_driver_exit':
qcom_qseecom_uefisecapp.c:(.exit.text+0x1c): undefined reference to `auxiliary_driver_unregister'
Full randconfig file is attached.
CONFIG_AUXILIARY_BUS is not set/enabled.
--
~Randy
[-- Attachment #2: config-r6997.gz --]
[-- Type: application/gzip, Size: 31687 bytes --]
prev parent reply other threads:[~2023-09-15 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 2:01 linux-next: Tree for Sep 15 Stephen Rothwell
2023-09-15 19:20 ` linux-next: Tree for Sep 15 (drivers/mfd/cs42l43.o) Randy Dunlap
2023-09-18 14:40 ` Lee Jones
2023-09-18 19:25 ` Randy Dunlap
2023-09-19 14:21 ` Lee Jones
2023-09-15 19:30 ` Randy Dunlap [this message]
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=9f156fa6-e5aa-4cb2-ab2b-b67fd8fc4840@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=luzmaximilian@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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