From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Chanwoo Choi <cw00.choi@samsung•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Leonard Crestez <leonard.crestez@nxp•com>
Subject: linux-next: build failure after merge of the devfreq tree
Date: Fri, 22 Nov 2019 15:59:41 +1100 [thread overview]
Message-ID: <20191122155941.4c8e3bd1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Hi all,
After merging the devfreq tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "__arm_smccc_smc" [drivers/devfreq/imx8m-ddrc.ko] undefined!
Caused by commit
1fcfb874236e ("PM / devfreq: Add dynamic scaling for imx8m ddr controller")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-22 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 4:59 Stephen Rothwell [this message]
2019-11-22 21:54 ` linux-next: build failure after merge of the devfreq tree Leonard Crestez
-- strict thread matches above, loose matches on Subject: below --
2019-12-13 1:49 Stephen Rothwell
2025-05-12 2:09 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=20191122155941.4c8e3bd1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cw00.choi@samsung$(echo .)com \
--cc=leonard.crestez@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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