From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the scmi tree
Date: Thu, 30 Nov 2023 22:01:37 +0000 [thread overview]
Message-ID: <20231130220137.pglo3n5g3n5zuudy@bogus> (raw)
In-Reply-To: <20231201085914.4ad45eb2@canb.auug.org.au>
On Fri, Dec 01, 2023 at 08:59:14AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the scmi tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arm-linux-gnueabi-ld: drivers/firmware/arm_scmi/perf.o: in function `scmi_dvfs_freq_set':
> perf.c:(.text+0xc8c): undefined reference to `__aeabi_uldivmod'
>
> Caused by commit
>
> eb55fbef8913 ("firmware: arm_scmi: Fix possible frequency truncation when using level indexing mode")
>
> I have used the scmi tree from next-20231130 for today.
Thanks for the report, I will fix it ASAP.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-11-30 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:59 linux-next: build failure after merge of the scmi tree Stephen Rothwell
2023-11-30 22:01 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 9:37 Stephen Rothwell
2025-05-02 9:44 ` Sudeep Holla
2024-08-28 0:15 Stephen Rothwell
2024-08-28 5:29 ` Peng Fan
2024-08-28 8:48 ` Sudeep Holla
2023-10-05 23:39 Stephen Rothwell
2023-10-06 6:50 ` Sudeep Holla
2022-11-08 22:29 Stephen Rothwell
2022-11-09 8:58 ` Sudeep Holla
2022-07-01 0:36 Stephen Rothwell
2022-07-01 8:13 ` Sudeep Holla
2020-07-08 23:58 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=20231130220137.pglo3n5g3n5zuudy@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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