public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sudeep Holla <sudeep.holla@arm•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the scmi tree
Date: Fri, 1 Dec 2023 08:59:14 +1100	[thread overview]
Message-ID: <20231201085914.4ad45eb2@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2023-11-30 21:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 21:59 Stephen Rothwell [this message]
2023-11-30 22:01 ` linux-next: build failure after merge of the scmi tree Sudeep Holla
  -- 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=20231201085914.4ad45eb2@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sudeep.holla@arm$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox